RE: FOP memory usage

On Sat, 2001-11-10 at 06:09, Branham, Paul wrote: > Would it be possible to show a small example of how this is accomplished? > > FOP and SVG are looking to be a good alternative to our current reporting > solution, but the current difficulty we are having is that I can't print out > large report

Re: FOP memory usage

Hey folks I guess I should have said, "no explicit garbage collection was performed". There is a compiled-in debugging option that forces FOP to to a System.gc() before printing the memory stats, but many applications of FOP will be long lived so asynchronous gc is better. So, GC is definitely do

Re: FOP memory usage

If you're generating the FO with XSLT, you could try starting a new page sequence every x nodes (rows). "Maring, Steve" wrote: > > OK. I tried the page-sequence thing at the only possible break points in my > data, and went from a 90MB memory footprint down to 28MB. But I also went > from a

Re: [REDESIGN] Initial cut at Layout Manager

At 12:05 AM 11/10/01 +0100, Karen Lease wrote: >Hi all, >An initial version of the Layout Manager classes (package >org.apache.fop.layoutmgr) is now in CVS, plus some related changes in >Area (up for discussion; this is just past the pseudocode point, but at >least it builds :-) and in the fo/pagi

cvs commit: xml-fop/src/org/apache/fop/fo FObjMixed.java

klease 01/11/09 15:04:21 Modified:src/org/apache/fop/fo FObjMixed.java Log: Fix an NPE Revision ChangesPath 1.15 +2 -1 xml-fop/src/org/apache/fop/fo/FObjMixed.java Index: FObjMixed.java ===

cvs commit: xml-fop/src/org/apache/fop/layoutmgr AbstractLayoutManager.java PageLayoutManager.java

klease 01/11/09 15:03:54 Modified:src/org/apache/fop/layoutmgr AbstractLayoutManager.java PageLayoutManager.java Log: Fix a couple of NPE Revision ChangesPath 1.2 +2 -2 xml-fop/src/org/apache/fop/layoutmgr/AbstractLayoutManager.java

[REDESIGN] Initial cut at Layout Manager

Hi all, An initial version of the Layout Manager classes (package org.apache.fop.layoutmgr) is now in CVS, plus some related changes in Area (up for discussion; this is just past the pseudocode point, but at least it builds :-) and in the fo/pagination classes. Needless to say, it does nothing use

cvs commit: xml-fop/src/org/apache/fop/apps StreamRenderer.java

klease 01/11/09 14:39:23 Modified:src/org/apache/fop/apps StreamRenderer.java Log: Remove call to PageSequence.format Revision ChangesPath 1.9 +5 -5 xml-fop/src/org/apache/fop/apps/StreamRenderer.java Index: StreamRenderer.java

cvs commit: xml-fop/src/org/apache/fop/fo/pagination PageSequence.java

klease 01/11/09 14:37:40 Modified:src/org/apache/fop/fo/pagination PageSequence.java Log: Start to use layout managers and comment out a bunch of (temporarily) unusable code Revision ChangesPath 1.43 +389 -283 xml-fop/src/org/apache/fop/fo/pagination/PageSequence.

cvs commit: xml-fop/src/org/apache/fop/fo/pagination SimplePageMaster.java RegionStart.java RegionEnd.java RegionBefore.java RegionAfter.java RegionBody.java Region.java

klease 01/11/09 14:31:51 Modified:src/org/apache/fop/fo/pagination SimplePageMaster.java RegionStart.java RegionEnd.java RegionBefore.java RegionAfter.java RegionBody.java Region.java Log: Rework the page creation process and prepare

cvs commit: xml-fop/src/org/apache/fop/layout PageMaster.java

klease 01/11/09 14:21:28 Modified:src/org/apache/fop/layout PageMaster.java Log: PageMaster uses a PageViewport object Revision ChangesPath 1.12 +65 -57xml-fop/src/org/apache/fop/layout/PageMaster.java Index: PageMaster.java =

cvs commit: xml-fop/src/org/apache/fop/render AbstractRenderer.java

klease 01/11/09 14:16:26 Modified:src/org/apache/fop/render AbstractRenderer.java Log: Rename Region to RegionReference in package area Revision ChangesPath 1.8 +8 -8 xml-fop/src/org/apache/fop/render/AbstractRenderer.java Index: AbstractRenderer.java

cvs commit: xml-fop/src/org/apache/fop/render/xml XMLRenderer.java

klease 01/11/09 14:15:45 Modified:src/org/apache/fop/render/xml XMLRenderer.java Log: Rename Region to RegionReference in package area Revision ChangesPath 1.32 +7 -7 xml-fop/src/org/apache/fop/render/xml/XMLRenderer.java Index: XMLRenderer.java ===

cvs commit: xml-fop/src/org/apache/fop/tools AreaTreeBuilder.java

klease 01/11/09 14:14:37 Modified:src/org/apache/fop/tools AreaTreeBuilder.java Log: Rename Region to RegionReference in package area Revision ChangesPath 1.4 +15 -15xml-fop/src/org/apache/fop/tools/AreaTreeBuilder.java Index: AreaTreeBuilder.java =

cvs commit: xml-fop/src/org/apache/fop/fo/pagination RegionBA.java RegionSE.java RegionBASE.java

klease 01/11/09 14:12:34 Added: src/org/apache/fop/fo/pagination RegionBA.java RegionSE.java RegionBASE.java Log: Base classes for before/after, start/end Region Revision ChangesPath 1.1 xml-fop/src/org/apache/fop/fo/pagination

cvs commit: xml-fop/src/org/apache/fop/fo/flow StaticContent.java

klease 01/11/09 14:11:14 Modified:src/org/apache/fop/fo/flow StaticContent.java Log: Comment out all layout code for now Revision ChangesPath 1.21 +45 -45xml-fop/src/org/apache/fop/fo/flow/StaticContent.java Index: StaticContent.java

cvs commit: xml-fop/src/org/apache/fop/fo/flow Block.java Flow.java

klease 01/11/09 14:08:49 Modified:src/org/apache/fop/fo/flow Block.java Flow.java Log: Start hooking in the layoutmanager Revision ChangesPath 1.44 +8 -1 xml-fop/src/org/apache/fop/fo/flow/Block.java Index: Block.java ===

cvs commit: xml-fop/src/org/apache/fop/fo FObj.java

klease 01/11/09 14:04:58 Modified:src/org/apache/fop/fo FObj.java Log: Add layout manager related methods Revision ChangesPath 1.23 +17 -1 xml-fop/src/org/apache/fop/fo/FObj.java Index: FObj.java ==

cvs commit: xml-fop/src/org/apache/fop/area Area.java BeforeFloat.java Block.java BodyRegion.java Flow.java Footnote.java MainReference.java Page.java RegionViewport.java Span.java

klease 01/11/09 14:02:35 Modified:src/org/apache/fop/area Area.java BeforeFloat.java Block.java BodyRegion.java Flow.java Footnote.java MainReference.java Page.java RegionViewport.java Span.java Log: Add some m

cvs commit: xml-fop/src/org/apache/fop/area RegionReference.java

klease 01/11/09 14:00:04 Added: src/org/apache/fop/area RegionReference.java Log: Replaces Region.java to avoid naming conflicts with fo/pagination/Region Revision ChangesPath 1.1 xml-fop/src/org/apache/fop/area/RegionReference.java Index: Region

cvs commit: xml-fop/src/org/apache/fop/area BlockParent.java

klease 01/11/09 13:59:30 Added: src/org/apache/fop/area BlockParent.java Log: Parent for areas which stack Block children Revision ChangesPath 1.1 xml-fop/src/org/apache/fop/area/BlockParent.java Index: BlockParent.java

cvs commit: xml-fop/src/org/apache/fop/area MinOptMax.java

klease 01/11/09 13:59:02 Added: src/org/apache/fop/area MinOptMax.java Log: Used in layout calculations Revision ChangesPath 1.1 xml-fop/src/org/apache/fop/area/MinOptMax.java Index: MinOptMax.java ==

cvs commit: xml-fop/src/org/apache/fop/layoutmgr AbstractLayoutManager.java BlockStackingLayoutManager.java BreakCost.java FlowLayoutManager.java LayoutManager.java PageLayoutManager.java SpaceSpecifier.java SplitContext.java

klease 01/11/09 13:57:47 Added: src/org/apache/fop/layoutmgr AbstractLayoutManager.java BlockStackingLayoutManager.java BreakCost.java FlowLayoutManager.java LayoutManager.java PageLayoutManager.java SpaceSpecifi

cvs commit: xml-fop/src/org/apache/fop/layoutmgr - New directory

klease 01/11/09 13:56:34 xml-fop/src/org/apache/fop/layoutmgr - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: FOP memory usage

OK. I tried the page-sequence thing at the only possible break points in my data, and went from a 90MB memory footprint down to 28MB. But I also went from a 17 page PDF to a 105 page PDF. STUPID QUESTION: Is there a way to have a page-sequence not automate a page break? Thanks. -Steve -

RE: FOP memory usage

Would it be possible to show a small example of how this is accomplished? FOP and SVG are looking to be a good alternative to our current reporting solution, but the current difficulty we are having is that I can't print out large reports. Thanks in advance, Paul Branham [EMAIL PROTECTED] 24/7

Re: FOP memory usage

Indeed, thanks to a recommendation from Mr. Lillywhite to use a sequence for each of my pages instead of one sequence for all, my memory footprint for a 500 page report went from 270+ MB to 1.4 MB. This was using 0.20.2 dave On Friday, November 9, 2001, at 12:31 PM, Lloyd McKenzie/CanWest

Re: FOP memory usage

I'm not sure if this will help or not, but it worked well for me. I was trying to process a 64 MB document, and it was taking DAYS and was eating gobs of memory. I did some wading through the code, looking for ways to optimize. I found a couple of places to reduce memory, but nothing substanti

Re: FOP memory usage

Make sure you're using -hotspot. Try setting the initial and max heap size to 256M if you have it. Turn on verbose garbage collection to see what's happening. Even though it says 'No garbage collection was performed, I'm not sure that's accurate (see below). Also sometimes the total memory used is

AW: FOP memory usage

Well, the problem with page-number-citations is, that he doesn't know the page number in the beginning, so he waits until he gets it and holds all pages in memory, i think. -Ursprüngliche Nachricht- Von: Jens Kühnberger [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 9. November 2001 16:08

Re: FOP memory usage

I also had this problem. To render a fo to pdf (around 100 pages) allocated more then 150 MB. When I got rid of references (in my case page-number-citations) the allocated memory was just 40 MB. Regards, Jens Michail Bikoulis wrote: >You can read the following two related articles from t

leaders and start-indent

Dear FOP people, I'm getting strange behaviour from fo:leader when I set start-indent on the block that contains it. I have this: Hello World Hello World and I expect to get this [fixed-width font required to view sensibly]: Hello

RE: FOP memory usage

You can read the following two related articles from the archives: http://marc.theaimsgroup.com/?l=fop-dev&m=100034658526437&w=2 http://marc.theaimsgroup.com/?l=fop-dev&m=100482704631972&w=2 Your XML files sound huge, but if I remember correctly Mark Lillywhite has had success with very large XM

DO NOT REPLY [Bug 4767] New: - SVG text is distored in PDF output

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

FOP memory usage

I'm using fop-0.20.1. I started with a 650KB XML file that I transformed into a 4MB XSL:FO file. Running this file through FOP to generate a PDF used about 90MB of memory. Initial heap size: 807Kb Current heap size: 91637Kb Total memory used: 90829Kb Memory use is indicative; no GC was perform

DO NOT REPLY [Bug 4766] New: - SVG line thickness wrong in PDF

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cymk-jpeg-pictures

hallo   i have a problem with 4C-pictures. i generated from a rgb-pictures one cmyk-pictures. everytime when i produce a pdf with fop 20.2 the colors are very bad. when i open the pictures in photoshop and save without change again there are ok.   thank for help.

[AGAIN] Missing versions in Bugzilla

Hi. Sorry if you receive this mail once again. The first time I sent it I was not correctly subscribed to the mailing list. I would enter a bug relative to Fop 0.20.1 in the bugzilla database, but the version numbers for Fop are stopped to 0.17.0. Please, could the bugzilla mainteners add the

[GUMP] Build Failure - Fop

This email is autogenerated from the output from: Buildfile: build.xml init-avail: init-filters-xalan2: [copy] Copying 1

cvs commit: xml-fop/src/codegen foproperties.xml

keiron 01/11/09 03:42:12 Modified:src/codegen foproperties.xml Log: added master-reference Revision ChangesPath 1.26 +6 -0 xml-fop/src/codegen/foproperties.xml Index: foproperties.xml ===

RE: column spanned in multicolumn region

At 09:26 AM 11/9/01 GMT, [EMAIL PROTECTED] wrote: >I have tried it in fo:region-body , eg. number-columns-spanned="3" column-count="3" margin-bottom="1.2in" >margin-top="0.8in"/>, but it still can't work, anything wrong? Contain the image in an fo:block or fo:block-container, that has the 's

AW: column spanned in multicolumn region

What you tried is paradox! You tried to split the region-body into 3 columns and at the same time span it over 3 columns: spliting into 3 + spanning over 3 = 1 column So you'll have to specify the number-columns-spanned to a fo:block or something that shall be spanned over 3 columns! Gr

RE: column spanned in multicolumn region

hi, Thanks Zhu. I have tried it in fo:region-body , eg. , but it still can't work, anything wrong? Thank you. best rgds, ektan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL P