Paulo Soares <psoares <at> glintt.com> writes: > > That's probably related to IO contention, iText does a lot of small reads. If you do everything in memory > what do you get? In any case, iText doesn't lock anything and any thread performance problems should be > addressed to the JVM. > > Paulo >
Paulo: Thank you for your quick response. I just tried changing my output stream from FileOutputStream to ByteArrayOutputStream, and ran the test a few times; total elapsed time (for a test using 4 threads) went from 12400 ms to 11200 ms - only about 1 second faster. As for the JVM, I mentioned in my original posting that I tried using the same thread experiment replacing the iText code with simple java statements to open a pdf file, read characters one at a time, and count them; this test clearly proved that the multi-threading/multi-processing capabilities of my system are working well. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.1t3xt.com/docs/book.php
