On Nov 6, 2006, at 7:18 AM, Robert Greig wrote:
The problem is that with our hardware we can often keep writing for quite a long time, i.e. the reader "keeps up" therefore it can be a while before we ever see the kernel buffer filling up. In one application which did a lot of writing this caused a problem because it was never reading from the socket and our hearbeating mechanism was effectively not working.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.
This makes me wonder if by default we should use a separate thread for writing + closing. There's definitely some opportunities for tweaking the IO thread processing behavior to boost throughput.
-pete -- [EMAIL PROTECTED] - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
