There is always a way to improve the performance! Well, it depends on the
size of your objects, machine, and network.
You need to understand that it's a distributed system and it's obvious that
it will not so fast as ConcurrentMap.
Evgenii
2018-04-01 15:32 GMT+03:00 kvenkatramtreddy
Hi,
Thank you very much for your reply. I found that it is an issue with
Webserver. I can see now Ignite cache is giving results are around
1-millisecond to 14 milliseconds with onheapEnabled and without
onheapEnabled, results are around 3 milliseconds to 200 milliseconds.
Are these expected
Hi,
Well, you're testing here not Ignite, but your JAX-RS services and Liberty
server. Could you check it by removing the Ignite cache invocation at all?
I'm pretty sure that you will get almost the same results without Ignite.
If you want to check Ignite, you can use yardstick:
Hi,We have setup 3 node cluster with Replicated caches. Ignite starts with
our JAX-RS servvices on Liberty server.We have exposed an API and reading
the values from cache(no business logic). Just read it from Ignite cache and
return it and it is taking more than 6 seconds. We had run load test
