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:23:19 UTC

[jira] [Closed] (GEODE-6233) Prepopulate phase of benchmarks is taking too long

     [ https://issues.apache.org/jira/browse/GEODE-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen Nichols closed GEODE-6233.
-------------------------------

> Prepopulate phase of benchmarks is taking too long
> --------------------------------------------------
>
>                 Key: GEODE-6233
>                 URL: https://issues.apache.org/jira/browse/GEODE-6233
>             Project: Geode
>          Issue Type: Bug
>          Components: benchmarks
>            Reporter: Brian Rowe
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>         Attachments: number of entries in 1M entry test.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> We are seeing very strange behavior with the prepopulate phase of the benchmarks. With 10K keys, the prepopulate phase occasionally takes several minutes.
> Looking at the stats, we see that almost all of the data is loaded immediately, but there is a long tail of just a few new entries being created per second.  This appears to be the result a single or very small number of PutAll operations having a hard time completing their last few values.
> When we bump up the number of keys to 1M, we see similar behavior, but the initial burst is an even lower fraction of the data, and we're still only around 500K entries created after an hour of prepopulation.



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