NFOP performance problem

Question

We're using NFOP in a project (C#, ASP.NET 2.0) to ultimately return PDF files to the user.

The process currently goes like this:

Stored Procedure -> XML
XML -> XSLT -> XSL-FO
XSL-FO -> NFOP -> PDF

This works fine, the PDF is generated BEAUTIFULLY. The problem is that it takes 300+ seconds to do it. The ANTS profiler indicates that the problem is sitting in the

driver.run()

method inside of NFOP. It's not like this is a gargantuan amount of data, the size of the xsl-fo source going into the nfop driver object is ~980k. What's the most likely source and resolution of this problem?

ANY hints or tips or answers are most appreciated, we were supposed to head to VA scan at 11 am. :|

score 1 · Answer 1 · answered Jun 24 '10 at 08:55

1

have you considered FO.NET?

answered Jun 24 '10 at 08:55

Vincent De Smet

4,859
2
34
41

No, we'll take a look at that. Thanks! – Jay Stevens Jun 24 '10 at 12:48

score 0 · Answer 2 · answered Jun 22 '09 at 18:09

0

I suggest you use a freely available tool like VisualVM and profile your code. It can show you the problem quite fast.

answered Jun 22 '09 at 18:09

Robert Munteanu

67,031
36
206
278

1

Please see the question. We HAVE used a profiler. It doesn't tell us anything useful. This is why I've asked the question here. – Jay Stevens Jun 22 '09 at 18:10
A profiler will 'drill down' into driver.run(). Try a commercial one if VisualVM does not have what it takes. – Robert Munteanu Jun 22 '09 at 18:15

NFOP performance problem

2 Answers2