How many concurrent conversions can Aspose Words .Net do?

[puneetdudeja1]

We have integrated the Aspose License in our product successfully.

We did some load testing on the product and received the following results for converting a One Page Microsoft Word document to PDF:

- 1 Request = 1.6 Seconds (Per Converted Document)

- 5 Concurrent Requests = 1.9 Seconds

- 8 Concurrent Requests = 3.8 Seconds

- 9 Concurrent Requests = 5.3 Seconds

o At this load of 9 concurrent requests, we received one or two conversion failures.

- At 10 Concurrent Requests, the Library stops responding and the Documents are not converted to PDF any more.

Can you please share some benchmark details of the PDF Conversion library?

The source document we used and converted pdf document are attached with this thread.

[tilal.ahmad]

Hi Puneet,

Thanks for your inquiry. Unfortunately we have no benchmarks available for performance/memory tests yet. Because the processing time and memory usage fully depend on your documents and their complexity.

Aspose.Words needs few times more memory than document size to build model of the document (DOM) in memory. For example if your document's size is 1 MB, Aspose.Words needs 10-20 MB of RAM to build its DOM in memory. Multiplier depends on format because some formats are more compact than others. For example DOCX format is more compact than DOC and RTF, and DOC is more compact than RTF.

Furthermore, please note for concurrent conversion Aspose.Words is multithread safe as long as only one thread works on a document at a time. It is a typical scenario to have one thread working on one document. Different threads can safely work on different documents at the same time.

Please feel free to contact us for any further assistance.

Best regards,