You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2018/12/07 23:58:00 UTC
[jira] [Updated] (GEODE-6148) Improve the efficiency of
PrePopulateRegion and increase the key range
[ https://issues.apache.org/jira/browse/GEODE-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Smith updated GEODE-6148:
-----------------------------
Summary: Improve the efficiency of PrePopulateRegion and increase the key range (was: Improve the efficiency of PrePopulateRegion)
> Improve the efficiency of PrePopulateRegion and increase the key range
> ----------------------------------------------------------------------
>
> Key: GEODE-6148
> URL: https://issues.apache.org/jira/browse/GEODE-6148
> Project: Geode
> Issue Type: Improvement
> Components: benchmarks
> Reporter: Dan Smith
> Priority: Major
>
> The PrePopulateRegion task could be much faster if we take some of these steps:
> * Stop duplicating work - right now each server will put the entire key range, resulting in duplicate puts of the same keys
> * use multiple threads - each server populating the region could be using multiple threads to populate it faster. One option would be to use a parallelStream, there may be better choicse.
> * Use putAlls - putAlls in batches require fewer round trips than puts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)