• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

Firefox 3.5 eating up more and more CPU time

Started by cytan, 2009.09.23, 21:36:07

Previous topic - Next topic

cytan

Hi all,
   I'm wondering whether anybody is seeing this: When I first start firefox, it does not seem to hog the CPU, but leaving it up overnight, it seems to start hogging the CPU. Using top its using up more than 90% of the CPU time.

   When I'm typing this message, FF is doing something because I see nothing being shown on screen when I'm typing but is being buffered. What's going on?

cytan

FF version 3.5.3

ivan

I gave up on FF 3.5.3 for various reasons, using too much memory, accessing the HD every 30 seconds as well as taking over 40 seconds to start.

Apart from it being bloated and slow I have reverted to 3.5.2 for some sites and 3.0.12 for all others.

cytan

Quote from: ivan on 2009.09.24, 01:09:21
I gave up on FF 3.5.3 for various reasons, using too much memory, accessing the HD every 30 seconds as well as taking over 40 seconds to start.

Apart from it being bloated and slow I have reverted to 3.5.2 for some sites and 3.0.12 for all others.


I cleared the history database of FF and everything seems to speed up again. I'll see if this fixes the problem. Stay tuned.

cytan

Saijin_Naib

Its the SQLite database FF 3.x uses. Its friggin slow.

jep

I compacted the sqlite files, and FF 3.5.3 is somewhat faster after that... doesn't lock up as much and as long as before.

You have to use the vio (command line) tool to compact the larger file urlclassifier3.sqlite or what it's called.
The qt3 gui version just close on that one, but is so much easier to work with on the smaller files.

//Jan-Erik

cytan

Quote from: jep on 2009.09.24, 09:41:00
I compacted the sqlite files, and FF 3.5.3 is somewhat faster after that... doesn't lock up as much and as long as before.

You have to use the vio (command line) tool to compact the larger file urlclassifier3.sqlite or what it's called.
The qt3 gui version just close on that one, but is so much easier to work with on the smaller files.

//Jan-Erik

What is the name of the commandline tool?

cytan

cytan

Seems that "Clearing Recent History" under tools and deleting everything has stopped my system from eating up 100% CPU time. Previously, history was set to 90 days, but I've set it to 3 days now. Let's see how that works out.

cytan

jep

Quote from: cytan on 2009.09.24, 16:16:01
What is the name of the commandline tool?

cytan
========
Command line tool: SQLite 3.6.12 for OS/2
port by Andrew MacIntyre
Type: sqlite3ow C:\path\to\sqlitedb.sqlite
> VACUUM;
>.quit
========
GUI Tool SQLite Database Browser 1.3d (SQLite 3.6.6.1)
by Ruediger Ihle
downoad from hobbes
========
//Jan-Erik

rudi

#8
Just out of curiosity:

What do "pragma page_size;"  and "pragma temp_store;" report on the database file in question ?

rdconsult

Quote from: jep on 2009.09.25, 15:05:08
Quote from: cytan on 2009.09.24, 16:16:01
What is the name of the commandline tool?

cytan
========
Command line tool: SQLite 3.6.12 for OS/2
port by Andrew MacIntyre
Type: sqlite3ow C:\path\to\sqlitedb.sqlite
> VACUUM;
>.quit
========

GUI Tool SQLite Database Browser 1.3d (SQLite 3.6.6.1)
by Ruediger Ihle
downoad from hobbes
========
//Jan-Erik

Hallo Cytan,

have a look at UPSSV on Hobbes. It does the Phyical reorganisation of the FF Databases and deliver information about the DB s.

http://hobbes.nmsu.edu/download/pub/os2/apps/internet/misc/upssv-1.0rc3.zip

Reame.txt

0.    Summary

      Start with release 3.0 Firefox administer user profile data
      by SQLite databases. SQL databases requires maintenance schedules for
      physical reorganisation of the databases. This task -
      for some of the profile databases -  is triggered by Firefox ( online ),
      if an idle status of the system is detected.
      UPSSV offers the user a batch function of reorganisation (SQL Vaccum)
      all of the database of the user profile at downtime of the
      browser at his own convenience. UPSSV required execution time
      of about 120 sec on my test system (ThinkPad T23 1.13 GHz HPFS). 

end of snippet readme

Kind regards

Rainer