[ 
https://issues.apache.org/jira/browse/IGNITE-12087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911520#comment-16911520
 ] 

Dmitriy Pavlov commented on IGNITE-12087:
-----------------------------------------

[~mstepachev] could you take a look at this issue?

> Transactional putAll - significant performance drop on big batches of entries.
> ------------------------------------------------------------------------------
>
>                 Key: IGNITE-12087
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12087
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Pavel Pereslegin
>            Priority: Major
>
> After IGNITE-5227 have been fixed I found significant performance drop in 
> putAll operation.
> Insertion of 30_000 entries before IGNITE-5227 took ~1 second.
> After IGNITE-5227 - 130 seconds (~100x slower).
> I checked a different batch size:
> 10_000 - 10 seconds
> 20_000 - 48 seconds
> 30_000 - 130 seconds
> and I was not able to wait for the result of 100_000 entries.
> Reproducer
> {code:java}
> public class CheckPutAll extends GridCommonAbstractTest {
>     @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
>         IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
>         CacheConfiguration ccfg = new CacheConfiguration(DEFAULT_CACHE_NAME);
>         ccfg.setAtomicityMode(TRANSACTIONAL);
>         cfg.setCacheConfiguration(ccfg);
>         return cfg;
>     }
>     @Test
>     public void check() throws Exception {
>         int cnt = 30_000;
>         Map<Integer, Integer> data = new HashMap<>(U.capacity(cnt));
>         for (int i = 0; i < cnt; i++)
>             data.put(i, i);
>         Ignite node0 = startGrid(0);
>         IgniteCache<Integer, Integer> cache0 = 
> node0.cache(DEFAULT_CACHE_NAME);
>         cache0.putAll(data);
>     }
> }{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to