You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried different combinations of Thread count and Workload size:
360 Threads / 3000 Ops - PASSES
500 Threads / 3000 Ops - FAILS
500 Threads / 2000 Ops - PASSES
700 Threads / 2000 Ops - FAILS
There seems to be a correlation and threshold with Thread count and Workload size.
This problem only exists (fails) with Apache Geode1.11.0. This test passes with the original Thread cont (180) and Workload size (10,000) with Apache Geode1.9.2.
The text was updated successfully, but these errors were encountered:
jxblum
changed the title
Reset the Thread count (180) and Workload size (10,000) once the Apache Geode concurrency issues are resolved.
Reset the Thread count (180) and Workload size (10,000) once the Apache Geode concurrency issues are resolved
Jan 24, 2020
This change must be made to the
MultiThreadedHighlyConcurrentClientServerHttpSessionAccessIntegrationTests
class.When the Thread count is
180
and the Workload size is10,000
, the Apache Geode Server becomes non-responsive or unavailable (i.e. it fails)!I tried different combinations of Thread count and Workload size:
360 Threads / 3000 Ops - PASSES
500 Threads / 3000 Ops - FAILS
500 Threads / 2000 Ops - PASSES
700 Threads / 2000 Ops - FAILS
There seems to be a correlation and threshold with Thread count and Workload size.
This problem only exists (fails) with Apache Geode
1.11.0
. This test passes with the original Thread cont (180) and Workload size (10,000) with Apache Geode1.9.2
.The text was updated successfully, but these errors were encountered: