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




On 09/16/2011 08:31 PM, NoOp wrote:
On 09/16/2011 11:44 AM, Heinrich Stoellinger wrote:
Hello again,
On my Linux/LO 3.4.3 system, after some time of working with Base (ODBC connetcion
to MySQL), LO uses 90 to 100 p.c. of one of the 4 CPUs of my PC. When I then save
LO-Base, CPU-usage is normal again (for a while!). I don't really know what causes
this behaviour, could it have to to with backup copy creation? I find an aweful
lot of backup files in /home/rainermusik/.libreoffice/3/user/backup.
All of them have a filename something like "rmodbc.odb_9777.odb" and are of 0 (zero)
size. I wonder what's wrong.
Regards
H. Stoellinger

And what happens if you turn off auto backup?



Hi All,

Base worked well for me in Windows since it was created while I was running Windows, and for two years in Ubuntu until the Java for Linux was updated from 1.6.0_22 to 1.6.0_24 last spring. At that point Base became almost unusable. In a database with 2500 records, instead of going from the first record to the last record in about 1 second, the time became 25 to 30 seconds. When I looked at CPU usage. 1 core would be running at 100% during this time. Java 1.6.0_26 then came out, and the same problem existed. About 5 weeks ago someone started a thread titled something like "Base runs unacceptably slowly." One person left a post stating that in Linux you can have more than one version of Java installed at the same time and left the following instructions:
Overview:

1. Download the JRE archive (approx. 20 mb)
2. Extract in /tmp
3. as root, copy the extracted directory to /usr/lib/jvm
4. set this JRE as the JRE of choice in LO (Tools>Options>Java)
5. Exit LO & restart

Instructions:

1.Download jre-6u21-linux-i586.bin (for i386) or jre-6u21-linux-x64.bin for
x86_64 from
http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html#jre-6u21-b07-oth-JPR
JRE archive at ORACLE . Save to /tmp . Open Terminal and enter cd /tmp. Then do the following commands:
2.run it using: "sh jre-6u21-linux-i586.bin" . The JRE is now extracted to
/tmp/jre1.6.0_21/
3. copy to /usr/lib/jvm "sudo cp -a jre1.6.0_21/ /usr/lib/jvm"
4. Exit & restart office.  In Tools>Options>Java, choose 1.6.0_21. Exit &
restart office
5. Load you Base file & compare the speed.

If you want to remove it simply set the JRE back to the old one in
Tools>Options>Java & "sudo rm -rf /usr/lib/jvm/jre1.6.0_21/

This does not replace your current Java install in your browsers, or even show up in synaptic package manager. But it does show up as being available for LibreOffice. This solved my problem totally. 1.6.0_21 works very fast with Base. I haven't worried about security problems since the browsers are using the current versions, there isn't any plugin installed for 1.6.0_21 for the browsers, and also since it doesn't show up in synaptic. Does that mean there are not any risks? I don't know, but I would think any risk would be minimal.

The reason I think this might be your problem is because you have the same issue with CPU usage that I did.

Don




--

***
*


--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.