Apache JMeter VS Memcached

Usually, I would let organic users be my load test. However, I am working on a project that has an anticipated load on a new-to-my-team stack, so I'm looking into ways to load test.

I've seen tools like k6 (https://k6.io/), Artillery (https://www.artillery.io), and JMeter (https://jmeter.apache.org/).

I've been using Artillery, but it's hard to visualize the results.

What do you use?

Apache JMeter: This tool is an open-source application built on Java, designed specifically to test load functionality and performance. Developed by the Apache Software Foundation, JMeter is versatile, able to simulate loads across a wide range of services and protocols such as HTTP, HTTPS, JDBC, LDAP, and SOAP. With an extensible core that can be tailored with plugins, it provides the flexibility needed for different testing scenarios. Its intuitive GUI makes it easy for testers to design test plans and visualize the results in various ways.

I'll use Apache JMeter to do this experiment:

Thanks for the tip. Hows that compare to this tool? https://jmeter.apache.org/

Apache JMeter: Download and install JMeter from the official website (https://jmeter.apache.org/). Java Development Kit (JDK): JMeter requires Java, so ensure you have the latest JDK installed on your system. Postman: Install Postman from the official website (https://www.postman.com/downloads/).

The test scenario consists of querying for descriptions of different offers. During the test, I will collect data on memory and GC parameters using jConsole. I will run the test scenario using jMeter, which additionally will allow me to measure response times.

FYI some of our people internally use Jmeter. https://jmeter.apache.org/

It's not flashy so it probably wont get the standard "we are going to milk you for data" plan

Issue #5682Pull request #717 - Open Model Thread Group: avoid skipping rows from CSV Data Set Config

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.

JMeter https://jmeter.apache.org

Memcached

> Multiple clients racing can't be fixed.

Really? You can't think of a single way for multiple clients to operate on the same data without racing? (Here's a hint if you're still having trouble: https://github.com/memcached/memcached/wiki/Commands#cas.)

Memcached: A simple, open-source, distributed memory object caching system primarily used for caching strings. Best suited for lightweight, non-persistent caching needs.

Oh, thank you! I didn't realize that LRU Maintainer Thread was more than an expiration reaper. When it was first being introduced that was its first responsibility as lazy expiration removal by size eviction meant dead entries wasted capacity. It was all work in progress when I had read about it [1] and talked to dormando, so it got fuzzy. The compat code [2, 3] might have also thrown me off if I only looked at the setting and not the usage. Its a neat variant to all of these ideas.

[1] https://github.com/memcached/memcached/pull/97

stores session state in a session store like Memcached or Redis.

memcached has recently gained the ability to spill to disk: https://github.com/memcached/memcached/wiki/Extstore

we recently implemented this to grow our caches to >50TB

Django supports using Memcached as a cache backend. Memcached is a high-performance, distributed memory caching system that can be used to store cached data across multiple servers.