On Fri, May 20, 2016 at 11:02 PM, 'Mikeus' via libuv <[email protected]> wrote: > On Thu, 19 May 2016 22:02:09 +0300 > 'Mikeus' via libuv <...> wrote: > >> On Thu, 19 May 2016 17:47:52 +0200 >> Ben Noordhuis <...> wrote: >> >> > >> > I suspect you're writing data faster than the other end of the pipe >> > can read it. Am I right that handle->write_queue_size keeps growing? >> > >> >> I've added printing out the write_queue_size after write request creating in >> read_cb() >> and in the write callback function too. It shows the value is always either >> 0 or 6300144 (or 6300112) bytes. >> > > You appeared to be right, Ben. > After fixing a bug that I made when referencing the write_queue_size field, > it would be seen that the queue is growing:
What you can do is call uv_read_stop() when handle->write_queue_size exceeds a threshold, and call uv_read_start() when it drops below the threshold again. (You probably already figured that out but I mention it in case people come across this thread.) -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
