Noojee Fax 3.x Performance Testing
Tested on Intel(R) Xeon(R) CPU 3050 @ 2.13GHz with 1GB
CPU < 1%, Memory <1Mb
Each page takes approximately 30 seconds and the memory and cpu is consumed for the entire 30 seconds.
CPU 17%, Memory 59Mb, Conversion Time < 1s
Additional pages does not add significantly to the time taken.
CPU 17%, Memory 1Mb, Conversion Time <1s
As you can see the load due to the transmission and reciept of faxes is insignificant.
The main load issue is when converting Microsoft Word document and Acrobat PDF files.
Lets do the maths:
In a worst case scenario if 30 channels are being used to send MS-Word documents.
If each MS-Word document submitted contains only a single page to be faxed with the body of the email used as the cover sheet, then each MS-Word document will generate two pages to be faxed.
On average a single fax page takes 30 seconds to transmit so in a 60 second period each channel can send 2 fax pages for a total of 60 pages per minute. This ignores dial time which will actual increase the transmission time and reduce the load on the system, but for the sake of a doing a worst case scenario we will ignore this gain.
This means that at peak load the system needs to be able to process 30 MS-Word documents per minute.
Given that we can process an MS-Word document in under a second and we have 60 seconds to process 30 this isn't a problem.
Again given a worst case scenario you will need 30 * 59MB = 1.8GB of RAM.
|Channels||Xeon Cores||RAM||Hard Drive||OS|
|30||Dual Core||4 GB||5400 RPM||Ubuntu 10.04 64 bit|
|60||Quad Core||6 GB||5400 RPM||Ubuntu 10.04 64 bit|
|90||Dual Quad Core||8 GB||7200 RPM||Ubuntu 10.04 64 bit|
|120||Dual Quad Core||12 GB||7200 RPM||Ubuntu 10.04 64 bit|
|240||Dual Quad Core||20 GB||15K RPM or SSD||Ubuntu 10.04 64 bit|