700 User Akses Bareng, SIMRS-nya Nge-freeze? Mungkin Bottleneck-nya di Sini

🔀 Read in English 🇬🇧

Selamat Datang di Hajriah Fajar: Hidup Sehat & Cerdas di Era Digital

700 User Akses Bareng, SIMRS-nya Nge-freeze? Mungkin Bottleneck-nya di Sini

Pernah ngalamin? Pas jam sibuk, semua dokter dan admin input bareng, terus SIMRS tiba-tiba nge-freeze. Bukan error sih, tapi muter-muter gak selesai. Macet. Lemot. Bikin frustrasi.

“Kayaknya server-nya yang gak kuat.” Tapi apa benar begitu? Atau ada yang lebih dalam dari sekadar "kurang RAM"?

Mengenali Bottleneck

Bottleneck itu titik sempit dalam sistem yang bikin aliran data jadi macet. Analogi gampangnya: kamu punya 700 orang mau masuk bioskop, tapi pintunya cuma satu. Bisa kuat-kuatin ruang nontonnya, tapi kalau pintunya kecil, tetap aja antrean.

Dimana Saja Bottleneck Bisa Terjadi?

Bagian Sistem	Bottleneck Umum
Database	Query lambat, indeks gak optimal, transaksi besar serempak
Web server	Proses blocking, request gak diatur antrian
Client/browser	Form berat, banyak AJAX sekaligus, gak pakai debounce
Jaringan lokal	Switch overload, kabel usang, WiFi kepenuhan

Kasus SOAP Dokter: Input Banyak, Tabel Banyak

Waktu dokter simpan SOAP, biasanya data masuk ke banyak tabel sekaligus:

• SOAP header
• Obat (farmasi)
• Penunjang (laboratorium/radiologi)
• Antrian BPJS
• Billing

Kalau semua ini langsung dijalankan dalam satu transaksi, ya wajar kalau butuh waktu. Apalagi kalau 100 dokter klik “Simpan” bersamaan.

Solusi Potensial

• Queue background: Pisahkan proses lambat ke job terpisah
• Database optimization: Gunakan index, analisis slow query log
• Split transaksi: Simpan yang penting dulu, sisanya antri
• Load balancing: Pakai 2–3 server kalau sudah high load
• Monitoring real-time: Gunakan Prometheus, Grafana, atau custom dashboard

Studi: High-Concurrency Web App

Menurut studi ResearchGate 2019, pada sistem kesehatan dengan lebih dari 500 user aktif bersamaan, response time idealnya tetap di bawah 2 detik — jika menggunakan load balancing dan task queue.

Penutup: Jangan Cuma Tambah RAM

Menangani bottleneck itu kayak menangani kemacetan. Bukan cuma perlu jalan tol, tapi juga manajemen lampu merah, jalur alternatif, dan pengatur lalu lintas. SIMRS butuh pendekatan yang lebih manusiawi dan teknikal — bukan cuma upgrade spek.

---

Welcome to Hajriah Fajar: Living Smart & Healthy in the Digital Age

700 Users At Once, and SIMRS Freezes? Here's Where the Bottleneck Might Be

Ever seen your hospital system freeze during peak hours? All doctors clicking “Save” at once, and boom — system stalls. Not a crash. Just painfully... slow.

“Probably the server’s weak.” Maybe. But what if it’s deeper than that?

Understanding Bottlenecks

A bottleneck is the tightest point in a pipeline — the part that slows everything down. Even if your “hall” is big, a narrow entrance clogs the flow.

Common Bottleneck Zones

System Part	Usual Bottleneck
Database	Unoptimized queries, missing indexes, big simultaneous inserts
Web server	No queueing, blocking processes
Client/browser	Heavy forms, no debounce on AJAX
Local network	Old switches, weak WiFi, outdated cables

Doctor SOAP Case

Saving SOAP often triggers inserts into:

• SOAP main table
• Prescriptions
• Lab/Rad orders
• BPJS queue
• Billing

All done in one transaction? Multiplied by 100 doctors? Ouch.

What Can Be Done?

• Background queues
• Optimize database (indexes, slow logs)
• Split transactions
• Use load balancers
• Live monitoring (Prometheus, Grafana)

Research Insight

According to a 2019 study, even with 500+ concurrent users, response time should stay under 2s — if queues and balancing are used.

Closing

Solving performance issues isn’t just about throwing in more RAM. It’s about architecture, timing, and traffic control. Let’s make SIMRS smart, responsive — and less dramatic during rush hour.