3 ms·
That sort of what happens, there is just a configurable hard limit on how much new thread may be created that was hit by this benchmark. As mentioned in anothe
by kaba0 3y ago
That sort of what happens, there is just a configurable hard limit on how much new thread may be created that was hit by this benchmark.
As mentioned in another comment: jdk.virtualThreadScheduler.maxPoolSize
- Groxx 3y agoIs there no limit (ignoring outside limits, e.g. from the OS) for normal threads? I know people usually use limited size thread pools for a variety of reasons, but I can't say that I've actually tried to exceed limits in a Java process yet... That would indeed be a problem if it's not similarly unlimited by default. Configurable makes perfect sense, as does attempting to be conservative, but small hard-capped defaults are very obviously going to cause problems, especially while synchronized locks the carrier.
- Groxx 3y agoSince it's too late to edit, Java docs say: >The maximum number of platform threads available to the scheduler. It defaults to 256. Yeah, that's pretty small. >256 simultaneous synchronized calls doesn't seem particularly extreme, given how common its use is. Tho now I wonder if you can just set this to max-int and resume like normal, or if giant values do awful things internally...