You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Evgenii Zhuravlev <e....@gmail.com> on 2018/04/01 10:45:32 UTC
Re: Cache is too slow
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:
https://apacheignite.readme.io/docs/perfomance-benchmarking or some other
benchmarking tools, which will test only Ignite, without any web servers.
Regards,
Evgenii
2018-03-31 7:34 GMT+03:00 kvenkatramtreddy <kv...@gmail.com>:
> 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 with Gatling with 300 users and 10 seconds ramp up. Cache data also
> very small, it is around 200B All the requests are sent to same node.
> Gatling results
> System configuration 2 core CPU 8 GB RAM RHEL Configuration can found
> following link http://apache-ignite-users.70518.x6.nabble.com/file/
> t1700/example-ignite-sample.xml
>
> Please could help us to improve the performance. We are looking for read
> performance.
> ------------------------------
> Sent from the Apache Ignite Users mailing list archive
> <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
>
Re: Cache is too slow
Posted by Evgenii Zhuravlev <e....@gmail.com>.
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 <kv...@gmail.com>:
> 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 results , (or) still can I fine tune ignite cache.
>
> I can see 0 milliseconds with ConcurrentMap.
>
> Thanks & Regards,
> Venkat.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: Cache is too slow
Posted by kvenkatramtreddy <kv...@gmail.com>.
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 results , (or) still can I fine tune ignite cache.
I can see 0 milliseconds with ConcurrentMap.
Thanks & Regards,
Venkat.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/