Group docs comparison and viewer api - performance metrics for 50 pages- 100 pages and 500 pages


#21

Hi Prem,


Further to our previous reply, please note that it’s just the first moment when document rendering/comparison takes time. When same document is rendered/compared again with cache enabled, it doesn’t take more that 5 seconds (investigation performed on a 50 paged PDF document). However, document rendering at first moment does take some time.

Kind regards

#22

Hi Atir,


Many Thanks for your responses.

Yes agreed that with cache enabled, second time loading is fast. What we are looking at it is performance improvement in first time API call (viewer/comparison)?, once the user sees/views the document - we clean up the user folder (at server side)

Regards,
Prem Kumar

#23

Hi Prem,


We are pleased to apprise you that GroupDocs.Viewer for Java 17.2.0 has been released. We found that document rendering performance in latest version is improved than the older version of the API. Let us share our findings or investigation output:

Pages

Time in Sec. Old Version

Time in Sec. New Version

50

101.85

58.9

100

184.55

109.47


We used following documents for the investigation:
  • source50p.pdf
  • pdf100pages.pdf

Please find the latest version of API 17.2.0 here and share your experience. In order to further improve performance, we'd suggest you to render documents in multiple threads. For example, a 100 paged document can be divided into two chunks 1-50 and 51-100 pages and rendered in two threads. In this way all pages will be rendered much faster but please keep in mind that resources (CPU, RAM) consumption will be increased.

Kind regards

#24

Thanks Atir.


We will try out new viewer API and share our feedback with you.

Regards,
Prem Kumar

#25

Hi Prem,


You are welcome.
We will try out new viewer API and share our feedback with you.
Sure.

Best wishes

#26

Hi Atir,


As per our requirement, we are using viewer API for viewing PDF files. We pass PDF file as an input, viewer API eventually converts to Html5+CSS+SVG for rendering the pages in UI.

Need small clarification on viewer API features:
from groupdocs url:: https://www.groupdocs.com/products/viewer/java

whats the meaning of two features mentioned as below:
1. View document in PDF Form
2. View Document as it is (original form)
can you please give some example for both of them?

Thanks,
Prem Kumar



#27

Hi Prem,


Thanks for posting your concerns.
We’d like to elaborate you, what do these features mean and what is the difference between them?
1. View document in PDF Form
GroupDocs.Viewer for Java 3.x permits you to get any document in PDF form/format. For instance you have a MS Word or MS Excel document and you want to render it in/ get it in PDF format, you can achieve this using our document rendering API. Please go through this article in order to learn how this function can be attained. Furthermore, I’ve attached the sample and output documents (Rendering Sample.xlsx and Wordfile.docx documents into PDF format).
2. View Document as it is (original form)
This feature allows you to get document in its original form. For example, if you get stream of any document and you want to get the original document from it. You can use getFile method.
In this way, if you have a link on your webpage like this click here to get document and when user clicks on it, sample.docx will be downloaded in the browser. Whereas, if your browser supports viewing of such formatted documents, user can view them in browser as well just like chrome allows PDF viewing. Please go through this article in order to seek how this function can be achieved.

Hope it clears working and meaning of both features.
If you still have any query regarding them, do let us know.
Kind regards


#28

Hi Prem,


You are welcome.

Best wishes

#29

@prem.alex.kumar,

The issue you have found earlier (filed as VIEWERJAVA-1363) has been fixed in this update.