ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Mashenkov <andrey.mashen...@gmail.com>
Subject Re: Affinity Compute latency
Date Wed, 08 Nov 2017 08:44:37 GMT
Hi,

Most likely, first compute call will register a job class and it takes most
of time.
Make sure your class will not be unloaded between compute calls [1].

Try to make much more cycles to benchmark to make it run a few tens of
seconds and add warm-up cycles.
You can see how it done in Ignite yarstick [2] benchmarks [3].


[1] https://apacheignite.readme.io/docs/deployment-modes
[2]
https://apacheignite.readme.io/docs/perfomance-benchmarking#yardstick-ignite-benchmarks
[3] https://github.com/apache/ignite/tree/master/modules/yardstick

On Wed, Nov 8, 2017 at 7:58 AM, rajivgandhi <rajiv.gandhi@gmail.com> wrote:

> Hi All,
> We see a significant difference between the latency nos for
> affnityRun(single key)/compute(multiple keys) and get/getall. Our code is
> based on the below example:
> https://github.com/apache/ignite/blob/master/examples/
> src/main/java/org/apache/ignite/examples/datagrid/
> CacheAffinityExample.java
>
> The nos are as follows:
> 1. get/getall: 700 microseconds
> 2. affnityRun/Compute: 7 milliseconds
>
> Is this as expected?
>
> thanks,
> Rajeev
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 
Best regards,
Andrey V. Mashenkov

Mime
View raw message