On Fri, 7 Nov 2003, Gonzalo A. Arana wrote:
> 1) make statCPUUsage public? (I guess this is the best).
> If so, I would need to know cpu usage with better resolution than 1
> minute. Is it possible (using squid API rather than system calls)?
Won't give you very accurate information anyway..
> 2) try to check if compression is taking too much time in some other
> way?
> If so, how?
> Like record the number of consecutive calls to comm_select that didn't
> result in timeout, or some other ugly/unreliable hack like this?.
My instinctive reaction is to run the compression & decompression in a
separate thread. If the queue to the compression/decompression engine is
large, decrease the compression level used.
Regards
Henrik
Received on Fri Nov 07 2003 - 14:07:41 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:20:46 MST