ThreadPool doesn't eat up CPU as much as possible.


Recently I am playing with glib's threadpool APIs.   I found that, in
my program (on windows), the number unprocessed task of a pool is
accumulated when time is going on.

It seems that the threads in the pool don't have enough CPU time to
run,  but when I monitored my computer's CPU usage, it's far from
eaten up.

Is there anyway to the threads in pools to run a little longer?

If I changed to use thread instead of thread pool and set threads'
priority to URGENT, does it help?

Thanks a lot!

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]