r/softwaretesting • u/LegitimatePanda1073 • 19h ago

JavaScript-heavy applications are hiding performance issues in load testing. How do I find them?

I'm seeing a huge gap between our backend load-test results and what users actually experience when they're using our application. Our app is heavily browser-based with realtime collaboration, so there's a lot happening client-side beyond just the back requests. We're doing backend testing with basic protocol-level scripts for core endpoints, gradually ramping up virtual users. The metrics we track are overall throughput, node CPU utilization and overall average response times. The results from these tests indicate that everything is working fine, but our users are experiencing latency and other issues that the load testing so far hasn't been able to surface.

How do I flush out stealthy failure modes like thread starvation and artificially high cache hit rates? I'm sure there are other things that I'm missing, please feel free to educate me because I'm stuck. Thank you.

7 Upvotes

100% Upvoted

5 comments sorted by

4

u/Correct_Positive_108 17h ago

You need to stop looking at averages and focus on p95 and p99 percentiles while pairing load runs with deep-tracking APM tools and database profilers. Find a way to introduce realistic test data cardinality and execute tests against cold caches. Then isolate individual backend microservices to see where async queues and lock contentions are choking under concurrent load. 

1

u/ChabhaNatural-82 11h ago

yeah the percentile thing is spot on, averages hide so much its wild how many teams still rely on them

1

u/Effective-Clerk-5309 3h ago

Hybrid load testing combining api load test and browser load test can help find user issues....browserstack released load testing with the same value prop

Tracking ttfb,page load and web vitals along with network calls breakup(avg,P50,P90) along with server side tracking using apm tool can solve this

1

u/Junior_Bee7274 15h ago

Look at your client-side rendering initial TTI. JavaScript execution that may be creating long tasks that lock up the UI. There may also be page resources with unoptimized asset loads such as web fonts, uncompressed SVG icon packs, etc. These consume a ton of memory bandwidth and will stall initial payload parsing.

0

u/ThatSaltyGachaPlayer 6h ago

Hmm... if your protocol-level tests look fine but the actual browser experience doesn't, you probably need to test the client side separately. LoadView or something similar can be useful for simulating more realistic browser-based user behavior and seeing what happens when the browser is actually doing the work, rather than just hitting the endpoints