You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (Jira)" <ji...@apache.org> on 2022/06/03 20:28:00 UTC

[jira] [Created] (GEODE-10359) add a performance test for the ThreadMonitor feature

Darrel Schneider created GEODE-10359:
----------------------------------------

             Summary: add a performance test for the ThreadMonitor feature
                 Key: GEODE-10359
                 URL: https://issues.apache.org/jira/browse/GEODE-10359
             Project: Geode
          Issue Type: Test
          Components: core
            Reporter: Darrel Schneider


GEODE-8977 found that the thread monitor can impact performance of other healthy threads on a server.
We should have a JMH benchmark that measures the impact of the thread monitor on healthy threads. The test would have some number of threads that don't need to be doing anything (i.e. they can be stuck waiting for something). It should keep calling ThreadsMonitoringProcess.getThreadInfoMap at a high frequency. Meanwhile is should have a number of healthy threads that are doing repeated operations. The goal would be for the thread monitor to have minimal impact on the throughput of the healthy threads. The test could also see what the impact is if showLocks and/or batchCalls is true (these are getThreadInfoMap parameters).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)