We currently split to the threaded mode whenever the number of classes is more than one. This probably isn't very efficient and a bigger threshold would be better.

Comment From: dreis2211

In a vanilla app there is only one call anyhow that has more than 1 class passed and you can easily reach 200+ classes with actuator + web + security, which could probably benefit from splitting the work in half, so I'm wondering what threshold you have in mind, @philwebb ? Maybe classes > Runtime.availableProcessors()? But again, you have already around 130 classes with web alone.

Comment From: philwebb

I was thinking something fairly low, but more than 1. Perhaps I'll try something around 20.

Comment From: philwebb

I guess it won't make a difference for most current apps.