You can practice what you learned over there: https://15puzzle.netlify.app/. Source: almost 2 years ago

I spent 2 days practicing this and now get times in the 30 - 60 second range. I'm not a genius. So it's just not as hard as it seems. Try yourself: https://15puzzle.netlify.app/. Source: about 3 years ago

Gatling: An open-source load and performance testing tool primarily designed for web applications, Gatling utilizes a simple domain-specific language (DSL) for creating and maintaining test scripts. It supports HTTP/2 and allows recording and generation of scenarios directly from a browser. The tool also provides detailed performance reports that are easy to analyze. - Source: dev.to / 4 months ago

Performance and load testing are essential parts of GraphQL API testing. It ensures APIs can handle expected traffic volumes and respond within acceptable timeframes. You can use tools like Apache JMeter or Gatling to generate realistic loads and evaluate the API's performance under different scenarios. Techniques like batched queries and caching can help mitigate this issue. - Source: dev.to / about 1 year ago

New to the .NET community and trying to learn! I have used tools such as Apache JMeter (Java), gatling.io (Java) and Locust (Python) that are decent full featured web perf frameworks. Typically these integrate well with your code, and can be run as part of your unit/integration tests and produce offline reports. Source: over 1 year ago

Gatling , this is what we tested concurrency with. Setting up might take a while depending on your exp. But the tool is solid. Source: over 1 year ago

I used SpringBoot 3.0.2, GraalVM 22 (JVM mode), a MacOS 2,6 GHz 6-Core Intel Core i7, running 1000 users for 5 minutes. The idea was to test how memory consumption and CPU usage evolve. Below, I compared the footprint of these three solutions. I collected the total count of requests, throughput, memory consumption, and CPU usage using VisualVM and Gatling. - Source: dev.to / over 1 year ago