Hi,
If you're interested in the cache loading rather than in pure benchmarking
then I would suggest you using IgniteDataStreamer [1] as one of the fastest
way of a cache preloading.
Next if you're not going to use transaction then you can switch a cache to
ATOMIC mode. It will work faster.
I did simple sequential puts to the cache. The latencies kept spiking
intermittently to 30ms or higher.
The test took about 30 minutes to load 1M records. I am using the s3 ip finder
for discovery.
I would expect 1-2 ms at max putting to a cache per request, but 30 ms seems a
little higher.
This is usually a problem with one-threaded benchmarks.
1. You should add a warm up step, i.e. have your system work for about a
minute before starting measuring.
2. You should decide whether your application will be single-threaded or
multi-threaded. If it is multi-threaded, then your test
Hi,
I have configured 2 ignite servers with a heap size of 8G each.
Running with backups=1 and primary_sync mode.
Ignite servers are being used as a write behind cache for my Aurora
database.
I am trying to run a load test with 3 clients talking to the remote cache
in the 2 ignite servers.
All
