Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

Hi :)
It might be worth asking the Documentation Team how they build-up their guides?
Regards from
Tom :)  

From: David Ronis <>
To: Kracked_P_P---webmaster <> 
Sent: Friday, 12 April 2013, 20:27
Subject: Re: [libreoffice-users] Printing speed is glacial for large file

Hi Kracked,

That's what I'm doing.   I have 55 chapters in separate odt files and
use a master document (odm) to join them together, add a table of
contents and a cover page.  While I can't call LO's speed on some of the
individual chapter files blindingly fast, especially on the lager ones
with lots of graphics, it's fast enough.   The combined result is the


On Fri, 2013-04-12 at 15:18 -0400, Kracked_P_P---webmaster wrote:
I know that a professional writer of sci-fi and fantasy 
novels/paper-backs makes each chapter of his books a separate file, and 
he usually have 15 to 25 chapters.

I too have never heard of making a document more than 50 to 100 pages 
per file.  Just paging through it would be slow, even on my mid-range 
quad desktop with 4 GB of RAM.  To be honest, you might really find it 
better to break the document up by sections of no more than 50 pages or 
so, if possible.  I know there must be a way to define the starting page 
number for each chapter, or do the sectional page numbering in the 
footer - i.e. Section VII Page 35

On 04/12/2013 02:30 PM, Girvin Herr wrote:
That may or may not be true.  I am not familiar with the "free", etc. 
tools you mention, but they may be reporting system free memory, while 
the LO settings are limits for LO and may be topping out while there 
is still free system memory available.  I would take a look at the 
document file size and maybe triple that or more for the LO settings.  
Keep in mind that the file is compressed, so you should at least 
double that size, assuming a nominal 50% compression.  You could count 
the number of graphics in your document to get the max number of 
graphics setting.  1600 pages is a lot.  I have many "large" documents 
but I don't think any of them are 1600 pages.  Maybe hundreds of pages 
at the most. So I don't have any experience with a document that 
large.  Too bad LO doesn't have a memory pool usage dialog where one 
could see the memory usage.  Hint, hint to the devs.  With such a 
tool, we wouldn't need to be guessing about these settings.  I suggest 
you try File -> Properties and select the "General" tab.  There is a 
report on the document "Size" there.  Use the "Statistics" tab to see 
some other allocations, such as number of graphics.  Use of this data 
may help you zero in on acceptable memory allocation settings.
Hope this helps.
Girvin Herr

On 04/12/2013 09:08 AM, David Ronis wrote:
Hi Andrew,

Thanks for the reply.  In short, I'd already upped the memory options
for graphics (250MB total, 10MB per object, 100 objects) and tools like
free etc. show that I'm nowhere close to using all my memory (with or
without swapping enabled).


On Thu, 2013-04-11 at 22:04 -0400, Andrew Douglas Pitonyak wrote:
Have you attempted anything in particular to see if it allows for a
speed improvement? For example:

1. Check on memory usage. How high is it? Are you running out of 

2. Change graphics settings:

Tools > Options > LibreOffice > Memory

Then try increasing the memory for things such as graphics objects and
number of objects?

On 04/11/2013 01:59 PM, David Ronis wrote:
Hi Girvin,

Most of the graphics in the document are PDF pages that I've imported
into Draw and then cut and pasted them into an odt file, which in turn
is incorporated into the full document as laid out in the odm file.

Also normal scrolling of the odm document is horrendously slow as well
(minutes to scroll to the next page and redraw).


-----Original Message-----
From: Girvin Herr <>
Subject: Re: [libreoffice-users] Printing speed is glacial for large
Date: Thu, 11 Apr 2013 10:21:16 -0700

On 04/10/2013 03:13 PM, David Ronis wrote:
I have a project managed by an odm file that ends up being ca 1600 
long and contains several OLE objects, many graphics (some comprising
entire pages that started out as PDFs).  I find LO unbelievably slow
(even on such simple things as refreshing the window after remapping
it).  I've turned of recording/displaying changes,  upped the 
cache numbers, set the swap directory to a ram disk, and turned 
off all
to-disk swapping; nothing helps.   This is on a 2 CPU machine with 
of ram.

I'm currently trying  to print the project to a file (postscript
format).  This takes 4-6 hours, with 1 of the CPU's running at 
100% [BTW
is LO multi-threaded?].  The resulting postscript file is big, (about
350M) but not that big.

I'm on a Slackware Linux box.

Any suggestions?


There is a known problem with LO and Encapsulated PostScript (EPS)
graphics.  They slow down video rendering tremendously, causing
frustrating long scrolling time.  This may also cause a problem with
printing, I never tried it.  When I converted my document's EPS images
to JPEG, LO rendering/scrolling sped up tremendously.
Hope this helps.
(Fellow Slacker.)
Girvin Herr

Andrew Pitonyak
My Macro Document:

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.