On Mon, 23 Jan 2023 21:02:51 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
> jdb creates a ThreadStartRequest and ThreadDeathRequest so it can track all > created threads. It creates them with the SUSPEND_ALL policy. This is > unnecessary since jdb always immediately resumes all threads after doing the > thread bookkeeping. There is no interaction with the jdb user like there > would be with something like a Breakpoint event, and therefore no reason to > suspend. > > I was debugging an app that does nothing except create threads and allow them > to quickly exit. Changing the policy to SUSPEND_NONE sped up the execution of > the app by about 100x (that's 100 times faster, not 100%) This pull request has now been integrated. Changeset: 99521087 Author: Chris Plummer <cjplum...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/995210873497eb2400b7672096e6f3cac7fde9a6 Stats: 4 lines in 1 file changed: 3 ins; 0 del; 1 mod 8300811: jdb ThreadStartRequest and ThreadDeathRequest should use SUSPEND_NONE instead of SUSPEND_ALL Reviewed-by: alanb, sspitsyn ------------- PR: https://git.openjdk.org/jdk/pull/12152
