You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2019/08/20 16:09:00 UTC
[jira] [Created] (IGNITE-12087) Transactional putAll - significant
performance drop on big batches of entries.
Pavel Pereslegin created IGNITE-12087:
-----------------------------------------
Summary: 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
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;
// Prepare data.
Map<Integer, Integer> data = new HashMap<>(U.capacity(cnt));
for (int i = 0; i < cnt; i++)
data.put(i, i);
// Start 1 node.
Ignite node0 = startGrid(0);
node0.cluster().active(true);
node0.cluster().baselineAutoAdjustTimeout(0);
IgniteCache<Integer, Integer> cache0 = node0.cache(DEFAULT_CACHE_NAME);
// Load data.
cache0.putAll(data);
}
}{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)