[
https://issues.apache.org/jira/browse/GEODE-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-6191:
-----------------------------
Sprint: Current Iteration 5, Current Iteration 6 (was: Current Iteration 5)
> Investigate scaleability of benchmarks for different numbers of threads
> -----------------------------------------------------------------------
>
> Key: GEODE-6191
> URL: https://issues.apache.org/jira/browse/GEODE-6191
> Project: Geode
> Issue Type: Task
> Components: benchmarks
> Reporter: Dan Smith
> Assignee: Brian Rowe
> Priority: Major
>
> We should expect to see benchmark throughput scale linearly with the number
> of threads, up to the point where we start hitting either CPU or network
> limitations. If we do not scale, that indicates that either something in the
> benchmark framework or Geode itself is limiting us.
> In a couple of runs in google cloud with 48 threads vs 192 threads on 4 96
> CPU instances, we observed almost the same throughput (but which much higher
> latency) with 192 threads. CPU and network stats did not indicate full
> utilization.
> We should check the scaleability of these tests again after GEODE-6172 and
> GEODE-6148 are implemented. Try running the tests with increasing numbers of
> threads (eg 4,16,32,64,128,256,512, etc.) in AWS on c5.9xlarge instances and
> see when we stop scaling linearly and why.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
