Greg Wilkins

I have created PR #680 to change the test to just check the non controversial behaviour of a good servlet.

@maffe Do you have a read world problem with the existing mapping? If not, we are inclined to leave it as is.

> I will not create an Eclipse account (I don’t think I can receive e-mails at users.noreply.github.com and I don’t want to provide the information the Eclipse registration form requires),...

This will also need #11504

@sbordet @lorban because of pinning, I doubt this is a viable mode to run it.... but it would still be interesting to include this branch benchmarks just to see what...

Considering pinning, I think the current virtual thread mode is safe because we force reserved threads to 0, thus we will never tryExecute a producer task, so the producer should...

@sbordet @lorban I reverted the name `threadpool-hybrid` to `threadpool-virtual`. The new mode is now called `threadpool-all-virtual`.

@sbordet @lorban thoughts on this? Is this something we want to play with, or is pinning just too much of an issue to make it worthwhile?

@olamy the CI build is [green](https://jenkins.webtide.net/blue/organizations/jenkins/jetty.project/detail/PR-11501/19/pipeline). Any idea how I can make it update here?

@lorban @sbordet nudge!