Question about HawtDispatch NioManager on Windows

[mongonix]

Hi,

I used VisuamVM and YourKit profiler to profile my application. Both show me that NioManager and WindowsSelectorImpl have the biggest own CPU times among all classes in my application. This is strange, as I use only SerialQueues and no NIO dispatch sources at used at all.

I suspect that NioManager is always enabled, just for the case if someone would use NIO dispatch sources. If so, may be there is an option to disable it?
Or it used internally for any kind of queues?

Has anyone seen similar picture under profilers? May be profilers cannot correctly understand that WindowsSelectorImpl blocks in waiting state, but does not really account for the CPU time?

[Hiram Chirino]

Hi,

That's correct on all accounts. Seems like that's an issue with how
your profiler is accounting for the CPU time. the when the NIO
Manager enters the select() call, that thread should be considered to
be in an IO wait.

Regards,
Hiram

FuseSource
Web: http://fusesource.com/

[mongonix]

OK. Thanks for this clarification. No need to worry then ;-)