Isn't so computationally-hard, i just think about the idea of fragment pieces os code that have a loop, few minutes ago reading libuv book, i take a look at uv_async, worth it ?
On Saturday, February 1, 2014 9:16:04 AM UTC-2, Fedor Indutny wrote: > > Hi Eduardo! > > This really depends on how computationally-hard is your "queued" work, > if it is - then you are definitely doing it in a best possible way. > However, if it is very fast and simple, queueing it in thread pool may > only add additional latency without giving any improvement. > > Cheers, > Fedor. > > On Sat, Feb 1, 2014 at 3:09 PM, Eduardo Nunes Pereira > <[email protected] <javascript:>> wrote: > > Hi, > > > > I'm using uv_queue_work to improve a uv_read_start, so when have > something > > to read the uv_queue_work is called and do the job of parse the on_read > > data. So my question is, that is a good approach ? > > > > -- > > 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] <javascript:>. > > To post to this group, send email to [email protected]<javascript:>. > > > Visit this group at http://groups.google.com/group/libuv. > > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/groups/opt_out.
