java - If most of my Play code is blocking anyway, does it make sense to increase the number of threads? -

i have read lot how play's non-blocking approach works. ideally, incoming requests supposed blazing fast, off-loading heavy-duty work worker thread, , returning pool servicing more requests. that's 1 of reasons pool of application threads close number of available cores on machine's cpu. numerous sources warn against tinkering pool @ all.

let's face though. in reality, not part of codebase can made purely non-blocking. in fact, bigger application became, more started resembling traditional java-based server app. alternative making non-blocking , going around commodity jvm frameworks costly.

i started questioning play's original proposition. question should increase default thread pool? have unexpected consequences (besides, of course, increasing memory footprint)?