Hmm, my docs are tiny compared to that. Are you using XIncludes, olinks, and 
profiling?
 
Here's how I'm calling xsltproc in my build.bat file:

call xsltproc.exe 
        --nonet 
        --xinclude 
        --stringparam profile.condition %conditions% 
        --stringparam olink.debug 0 
        --stringparam collect.xref.targets "no" 
        --output %output_file%  
        --stringparam insert.xref.page.number yes 
        --stringparam insert.olink.page.number maybe  
        --stringparam target.database.document %olink_file%  
        --stringparam current.docid %doc_id% 
        %xsl_file% 
        %book_file% 
 
Regards,
Jeff

________________________________

From: [email protected] [mailto:[email protected]] 
Sent: 2012-03-09 03:06
To: [email protected]; Jeff Powanda; [email protected]
Cc: [email protected]
Subject: Re: [docbook-apps] Re: VirtualBox DocBook 5.0 VM


One more bit of info. I just ran a 1200 page doc (XP/2Gb/xsltproc) and it used 
about 230 MB of memory to churn through that doc.
 
In a message dated 3/9/2012 2:44:36 P.M. Pacific Standard Time, 
[email protected] writes:

                Jeff,
        I routinely process books over 400 pages (XP/2Gb/xsltproc) and rarely 
see a memory error. However, when I DO see one, it is because I have done 
something wacky in the XSL or have done something in the XML that was "legal" 
but not supported in the XSL. Rare though.
         
        What command line switches are you using?
         
        Regards,
        Dean Nelson
         
        In a message dated 3/9/2012 2:22:48 P.M. Pacific Standard Time, 
[email protected] writes:

                
                I'm using the Windows version of xsltproc.
                
                xsltproc worked fine on our smaller manuals (~50 pages), but it 
wasn't able to handle our largest books (~400 pages). I need to be able to 
build all the manuals on the writers' machines, which are Windows 7 or Windows 
XP laptops with only 2 GB of RAM. Xsltproc couldn't seem to handle those 
constraints. Saxon+Xerces can.
                
                If other people are using xsltproc under similar constraints on 
Windows and it's working fine, perhaps I'm doing something wrong.
                
                Regards,
                Jeff
                
                
                
                -----Original Message-----
                From: Tom Browder [mailto:[email protected]] 
                Sent: 2012-03-09 09:31
                To: Jeff Powanda
                Cc: Docbook Apps Help list
                Subject: Re: [docbook-apps] Re: VirtualBox DocBook 5.0 VM
                
                On Fri, Mar 9, 2012 at 11:25, Jeff Powanda 
<[email protected]> wrote:
                > Ok, thanks. I switched from xsltproc a few years ago when it 
was 
                > unable to process our largest manuals (it ran out  of memory).
                
                Was that a Windows version, or *unix?
                
                Size of manual?
                
                I'm sure libxslt folks would love to hear about that whichever 
system it was on.
                
                -Tom
                
                
---------------------------------------------------------------------
                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]

Reply via email to