You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Owen Nichols (JIRA)" <ji...@apache.org> on 2019/04/24 22:24:06 UTC

[jira] [Closed] (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 ]

Owen Nichols closed GEODE-6148.
-------------------------------

> 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
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We are currently running with a keyRange of 1000, which may be skewing our results. We want to run with a much larger key range, which means prepopulating more data. 
> 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.
> Acceptance:
> * All benchmarks can finish their prepopulation step in 30 seconds or less on reasonable hardware.
> * We set a fixed key range that is somewhere between 100 thousand and 100 million, whatever is most reasonable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)