Re: [hylafax-users] Document conversion failed

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Darren Nickerson wrote:

> Whereas HylaFAX used to bog down with faxq consuming 99% CPU and jobs 
> submitting _VERY_ slowly, it should now be pretty zippy.


I can't say that I recall the last time I saw faxq consume 99% CPU (or 
anything close to even half of it)... and I routinely stuff between 500 
or 1000 jobs into the outbound queue... this without the major refactoring.

I did look through all of the code changes in that work, and I can't see 
where any significant number of CPU cycles would be getting saved.  I'd 
enjoy seeing some real statistical comparisons of faxq performance 
between 4.3.4 and 4.4.0... and then 5.1.8.  ;-)

Thanks,

Lee.


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*