[
https://issues.apache.org/jira/browse/GEODE-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Rowe resolved GEODE-6234.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
This issue appears solved by increasing the key range from 10k to 1M which was
done as part of the fix for GEODE-6233,
> PartionedPutBenchmark shows a dramatic drop off at high thread counts
> ---------------------------------------------------------------------
>
> Key: GEODE-6234
> URL: https://issues.apache.org/jira/browse/GEODE-6234
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
> Reporter: Brian Rowe
> Priority: Major
> Fix For: 1.9.0
>
>
> When running the PartionedPutBenchmark with an increasing number of threads,
> in addition to hitting a wall around 64 threads (already tracked as
> GEODE-6191), we see the total number of operations plummet as we hit 256
> threads (this is using one client and two servers, all c5.9xlarge AWS
> instances, benchmarking Geode 1.8). The operations at that point range from
> 1/3 to less than 1/10 the operations we see with 64 threads.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
