Bug 51677 - [PATCH] Small logging performance fix for BreakingAlgorithm
Summary: [PATCH] Small logging performance fix for BreakingAlgorithm
Status: CLOSED WONTFIX
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: page-master/layout (show other bugs)
Version: trunk
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-18 12:44 UTC by Sergey Vladimirov
Modified: 2012-04-30 00:17 UTC (History)
0 users



Attachments
Patch (2.51 KB, patch)
2011-08-18 12:44 UTC, Sergey Vladimirov
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Vladimirov 2011-08-18 12:44:27 UTC
I have 2Mb FO document. FO converts it to PDF in 65-70 sec. Using "poor man's profiler" i optimized some logs calls in BreakingAlgorithm class. Now FO converts document in 54-55 seconds.

Document can be provided, if needed.
Comment 1 Sergey Vladimirov 2011-08-18 12:44:58 UTC
Created attachment 27405 [details]
Patch
Comment 2 Chris Bowditch 2011-08-22 13:19:20 UTC
Hi Sergey,

Thanks for the patch. It looks good in principal. Can you also attach some form of test case? If your own XSL-FO is private then please create an artificial example. Obviously I can create my own test case, but it is good practise to submit a test case with any code change.

Thanks,

Chris
Comment 3 Sergey Vladimirov 2011-08-22 14:13:39 UTC
Chris,

It's not a bugfix neither new feature, but a performance patch. So there is no exception neither unworking code that magically became working after applying the patch. What kind of test case you want me to create?

I still can provide example document, but the only different thing is execution time.

Best regards,
Sergey
Comment 4 Chris Bowditch 2011-08-22 16:11:08 UTC
Hi Sergey,

I understand it is not a bug and the change doesn't fix an error. I simply meant that it is good practice to supply a test file for every code change. Regardless of the affect the change has. If I make up a test file I may get very different results from you, and if I perceive no performance improvement then I would be reluctant to commit the change. If however, we use the same test file, then our results should be aligned. Do you see what I mean? Of course, it would be prudent for any developer to try out multiple test files, not just 1, but I still think it would be useful for you to provide a test XSL-FO.

Thanks,

Chris
Comment 5 Glenn Adams 2012-04-01 15:34:27 UTC
(In reply to comment #3)
> Chris,
> 
> It's not a bugfix neither new feature, but a performance patch. So there is no
> exception neither unworking code that magically became working after applying
> the patch. What kind of test case you want me to create?
> 
> I still can provide example document, but the only different thing is execution
> time.
> 
> Best regards,
> Sergey

Sergey, do you expect to provide a test FO file for verifying the impact of your performance patch? if not, then I will move this bug to resolved+wontfix, thanks Glenn
Comment 6 Sergey Vladimirov 2012-04-01 19:55:24 UTC
(In reply to comment #5)
> Sergey, do you expect to provide a test FO file for verifying the impact of
> your performance patch? if not, then I will move this bug to resolved+wontfix,
> thanks Glenn

Glenn,

I'm can't provide test file anymore.

Sergey
Comment 7 Glenn Adams 2012-04-30 00:14:45 UTC
batch transition resolved+wontfix to closed+wontfix
Comment 8 Glenn Adams 2012-04-30 00:17:13 UTC
batch transition resolved+wontfix to closed+wontfix; if you believe this remains a bug and can demonstrate it with appropriate input FO file and output PDF file (as applicable), then you may reopen