Re: Performance Question

2003-05-02 Thread Ryan . Asleson


Sorry, I should have included these details also:

Our PDFs are produced during a batch process, meaning the JVM is started
once and all PDFs are then created.  This, of course, means the JVM stays
"warm" and we can take full advantage of HotSpot compilation.

We also have implemented a style sheet cache, so once the style sheet has
been used once the compiled version is reused over and over, which
definitely helps performance.

All of our XML/XSLT interfaces use JAXP, meaning we can plug in different
XML/XSLT processors.  We currently use Saxon 6.5.2 because it's the
fastest, but it appears the recently-released Xalan 2.5 has closed the gap
considerably.

Even though the computer has 1 GB RAM available, we only allocate a max
heap size of 512 MB.





   
  [EMAIL PROTECTED] 
   
  ul.com   To:   [EMAIL PROTECTED]  
 
   cc:  
   
  05/02/2003 06:58     Subject:  Re: Performance 
Question  
  AM
   
  Please respond to 
   
  fop-user  
   

   

   





I have FOP running on a Pentium 4 2.54 GHz computer with 1 GB memory and
Win2000.  I use Saxon 6.5.2 as the XML parser and XSLT engine.  It also
uses custom XMLReaders to produce SAX events which are processed by FOP.

We usually see a PDF production rate of 8-9 pages per second, and we
sometimes produce PDFs that are 1500+ pages.  The only real problem with
FOP is some of the XSL style sheet tricks necessary to insert intermittent
page-sequences so FOP doesn't run out of memory.

Hope this helps.




  "Christian

  Neuroth" To:
<[EMAIL PROTECTED]>
  <[EMAIL PROTECTED]>cc:

   Subject:  Performance
Question
  04/30/2003 03:30

  AM

  Please respond to

  fop-user








In my company, we are currently using StreamServe to produce documents
(basically invoices).
50.000 docs/day, 3.000 prints, 47.000 pdf.
The final document averages 3 pages (there are some exceptions with up to
1000 pages - very rare, however), a document containing only one graphic
(logo).

I am puzzling whether I can shift from StreamServer to FOP. Are there any
people out there who apply FOP to achieve a similar volume? Is the
performance ok?









-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Performance Question

2003-05-02 Thread Ryan . Asleson

I have FOP running on a Pentium 4 2.54 GHz computer with 1 GB memory and
Win2000.  I use Saxon 6.5.2 as the XML parser and XSLT engine.  It also
uses custom XMLReaders to produce SAX events which are processed by FOP.

We usually see a PDF production rate of 8-9 pages per second, and we
sometimes produce PDFs that are 1500+ pages.  The only real problem with
FOP is some of the XSL style sheet tricks necessary to insert intermittent
page-sequences so FOP doesn't run out of memory.

Hope this helps.




   
  "Christian
   
  Neuroth" To:   <[EMAIL PROTECTED]>
 
  <[EMAIL PROTECTED]>cc:
 
   Subject:  Performance Question   
   
  04/30/2003 03:30  
   
  AM
   
  Please respond to 
   
  fop-user  
   

   

   





In my company, we are currently using StreamServe to produce documents
(basically invoices).
50.000 docs/day, 3.000 prints, 47.000 pdf.
The final document averages 3 pages (there are some exceptions with up to
1000 pages - very rare, however), a document containing only one graphic
(logo).

I am puzzling whether I can shift from StreamServer to FOP. Are there any
people out there who apply FOP to achieve a similar volume? Is the
performance ok?









-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Performance Question

2003-04-30 Thread J.Pietschmann
Christian Neuroth wrote:
50.000 docs/day, 3.000 prints, 47.000 pdf.
The final document averages 3 pages (there are some exceptions with up to
1000 pages - very rare, however), a document containing only one graphic
(logo).
A good rule of thumb is two pages per second on moderate hardware (Intel P4
1GHz), if the JVM is kept warm. If the documents share the graphic, FOP's
image cache is an advantage. This might fit, barely (1d=86.4ksec ~ 172 kpage
~ 50k documents). If you are batch processing, you can try to balance it
over several machines.
Run some benchmarks and make up your own mind.
J.Pietschmann
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Performance Question

2003-04-30 Thread Matthias Fischer
I tried to process lesser amounts of docs (muuch lesser volumes!) and got
into serious trouble. I have abbandoned FOP, but I must admit that there was
Cocoon inbetween.

Matthias Fischer

 -Original Message-
 From: Christian Neuroth [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, April 30, 2003 10:30 AM
 To: [EMAIL PROTECTED]
 Subject: Performance Question


 Hi list!

 I just downloaded FOP for some evaluation tests and it seems to
 be really
 great! :)

 In my company, we are currently using StreamServe to produce documents
 (basically invoices).
 50.000 docs/day, 3.000 prints, 47.000 pdf.
 The final document averages 3 pages (there are some exceptions
 with up to
 1000 pages - very rare, however), a document containing only one graphic
 (logo).

 I am puzzling whether I can shift from StreamServer to FOP. Are
 there any
 people out there who apply FOP to achieve a similar volume? Is the
 performance ok?

 Thanks

 Christian


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]