Good things come in batches, I suppose. My subconscious obviously wasn't done with this....
I moved all of the read infrastructure's .setValue()
actions into Runnables on the driver's subscription thread pool, instead of leaving them in Netty's receive callchain.
Check out the resulting response time stat:
v2.0.4.231061846
My module sales page is already updated.