D4R issues
Malcolm Hussain-Gambles (1596) 811 posts |
I didn’t read the size of the buffer, but the amount of data I was reading increased. int buffer_size = 131072 I’m trying to do some re-organisation of the main loop code tonight, which is proving more problematic than I first thought (it’s a tangled web) |
Colin (478) 2433 posts |
I wonder if the effect you are seeing is caused by setsockopt triggering callbacks. It would be interesting to know if you get the speed improvement with setsockopt replaced with:
MSG_WAITALL flag in socket recv will wait for the full request or timeout set by SO_RCVTIMEO or error but it will block while reading. You can’t read more than the buffer without blocking. |
Malcolm Hussain-Gambles (1596) 811 posts |
I’ve managed, after much pain, to reorganise the main processing loop. It was far too long and complex, so now it’s split into procedures. [Update] Suprisingly I just managed to do it using otter-browser |
Malcolm Hussain-Gambles (1596) 811 posts |
Version 0.10 has been done, so my next step is the 0.2x series – multiple downloads. This should be much more “fun” ;-) |