HylaFAX The world's most advanced open source fax server

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

[hylafax-users] Re[2]: Spooler performance



Hello Lee,

 Thank you for an answer.
 I think I used 'batches' word in wrong meaning.
 All faxes are to DIFFERENT destinations, so I think MaxBatchJobs is
 unacceptable here (sure if I correctly understood meaning of this
 parameter.)


 P.S.
 So, I just like to hear what options I have to improve my performance
 issues (more horse power or better buying commercial version with SQL
 support? will it help here?)...

 Thank you all for any help.

 P.P.S. Please ignore same post that can be submitted by moderator, I
 used wrong source address, sorry.

Friday, November 25, 2005 8:18:02 AM, you wrote:

LH> Mike Tkachuk wrote:

>> The faxq CPU time usage growing is not linear,
>> meaning that with 1000 jobs the load is ~5%, with 2000 jobs it's
>> like 10% and with 3000 jobs average CPU usage is ~50%.
>>

LH> What happens if you disable batching?  (You do that by setting 
LH> "MaxBatchJobs: 1" in /var/spool/hylafax/etc/config.)

LH> Thanks,

LH> Lee.



--
Mike Tkachuk


____________________ 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*




Project hosted by iFAX Solutions