ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@gridgain.com>
Subject Re: GridConcurrentFactory.CONCURRENCY_LEVEL
Date Tue, 10 Mar 2015 13:29:20 GMT
I agree, this makes iterations over map much longer.

Please create ticket in jira and remove the factory and run benchmarks
after that.

--
Yakov Zhdanov, Director R&D
*GridGain Systems*
www.gridgain.com

2015-03-08 21:45 GMT+03:00 Sergey Evdokimov <sevdokimov@gridgain.com>:

> Hello,
>
> Why we have so huge concurrency level for concurrent hash maps created by
> GridConcurrentFactory.newMap() ? By default concurrency level is 256, does
> we expect that 265 thread will update the map *at same time*? Huge
> concurrency level increases iteration time.
> When I set concurrency level to jvm default value (16) my benchmark became
> 73% faster (23000 operation/sec vs 40000 operation/sec). My benchmark just
> executes simple job on local node. GridTaskProcessor iterates over
> GridTaskProcessor#tasks on each task submit. Although
> GridTaskProcessor#tasks is empty iteration get a lot of time.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message