[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Re: RFR: 8300811: jdb ThreadStartRequest and ThreadDeathRequest should use SUSPEND_NONE instead of S
From:       Alan Bateman <alanb () openjdk ! org>
Date:       2023-01-30 19:16:54
Message-ID: egro_jihc9v0tcDe_7fHXgeiV_ALsLl5okZtWZl5zD4=.d2c97cd4-7028-4d4d-b8a9-11c9d5e26853 () github ! com
[Download RAW message or body]

On Mon, 23 Jan 2023 21:02:51 GMT, Chris Plummer <cjplummer@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%)

Marked as reviewed by alanb (Reviewer).

-------------

PR: https://git.openjdk.org/jdk/pull/12152


[prev in list] [next in list] [prev in thread] [next in thread]