On 06/11/06, Vinod Panicker <[EMAIL PROTECTED]> wrote:
The rationale is fine, but does the multi-threaded SocketIoProcessor use a thread pool or just two threads?
No it does not use a pool. It uses two threads per SocketIoProcessor where currently it uses one.
> The obvious solution is to limit the number of writes done in a given > loop but this then leads to throughput reduction. After much messing > about we found that using two threads allows reads and writes to run > "flat out" as much as possible. Wouldn't the bias be applicable for reads as well? It sounds like a case of inertia unless I'm missing something.
Reads were handled differently in the original code, it just reads enough up to the size of the buffer. RG
