Hi,

After my previous thread here, I started exploring other potential patterns 
for my project. I think the Idler pattern presented in the Utilities docs 
(http://docs.libuv.org/en/v1.x/guide/utilities.html#idler-pattern) would 
work well for my app, so I sketched it up briefly with my loop running with 
UV_RUN_DEFAULT.

I'm finding that if I call `uv_idle_start` even with a dummy callback, my 
app will spin up to 90-100% CPU immediately. If I never call that start, 
I'm at 0-1% (and of course just running the default loop). On profiling, it 
looks like my app spends a ton of energy going back and forth between 
uv__run_check and uv__io_poll.

Is there some gotcha to this pattern that I should be aware of? Or 
something particular I need to do to set it up correctly?

Thanks,
Nick

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/libuv/e9e2ed9e-477d-4386-9305-74d5333f26edn%40googlegroups.com.

Reply via email to