On 09/16/2011 07:03 PM, Don Myers wrote:
> 
> 
> 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:

Please provide a link to your bug reports (for both LO and Java). Thanks.
...


-- 
For unsubscribe instructions e-mail to: users+h...@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

Reply via email to