Is this other library flattening the form as well? That can get pricey,
computation-wise. Is it appending its changes to the existing PDF, or
rewriting everything? Are both Java libraries?
--Mark Storer
Senior Software Engineer
Cardiff.com
import legalese.Disclaimer;
Disclaimer<Cardiff> DisCard = null;
________________________________
From: Azùa Giovanni (KSXD 32) [mailto:[email protected]]
Sent: Tuesday, April 20, 2010 6:54 AM
To: Post all your questions about iText here
Subject: Re: [iText-questions] performance question
Hello Paulo,
I am perfectly aware of the benefits of iText, that's why I proposed it for our
project in the first place but it can be hard to convince the team lead and
colleagues to switch to a framework when it comes at a performance toll of 30%
overhead for the use-case at hand.
I didn't mean to start a flame but was actually fishing for rewrite
alternatives to improve the performance of our use-case ...
Best regards,
Giovanni
==============================================================================
Please access the attached hyperlink for an important electronic communications
disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
<http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html>
<http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
<http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html> >
==============================================================================
________________________________
From: Paulo Soares [mailto:[email protected] <mailto:[email protected]> ]
Sent: Tuesday, April 20, 2010 2:48 PM
To: Post all your questions about iText here
Subject: Re: [iText-questions] performance question
Hmm, there are lies, damn lies and statistics. While I don't dispute the 30%
let's see the probable causes for this:
- iText tries to do things correctly avoiding to cut corners that will come and
bite your later. Metadata writing, appearance generation and so on.
- iText is a generic PDF library. It reads, writes and modifies PDFs. Any
library designed with a narrower purpose can optimize the interested areas to
perform better.
- iText comes with source and can be extended, modified, altered. This implies
that a sensible and probably heavier structure must be in place to allow that.
If you have a closed source library with just a single purpose things can be
done faster as that's all it's going to do.
- com.itextpdf.text.pdf.PdfStamperImpl.close() is where everything is written
to file, if you avoid calling this nothing will come out.
- There are some speed and memory improvements in the pipeline but I don't know
how much % improvement will result or in what areas.
Paulo
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.801 / Virus Database: 271.1.1/2806 - Release Date: 04/20/10
05:45:00
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
iText-questions mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/itext-questions
Buy the iText book: http://www.itextpdf.com/book/
Check the site with examples before you ask questions:
http://www.1t3xt.info/examples/
You can also search the keywords list: http://1t3xt.info/tutorials/keywords/
