On Tue, 2 May 2006, Christoph Haas wrote:
By way of comparison my systems were thrashing badly even with 2Gb of ram
because mySQL wasn't using enough memory. Allowing it to grow to 1Gb ram
solved it almost entirely.
I just have 512 MB of RAM but you made me think about my server parameters.
Adjusting /etc/my.cnf is pretty much a necessity on large database
systems, or mysql will make extensive use of temporary files and things
can grind to a halt quickly. The default settings are only ok for
small systems or for testing.
While I used settings from the "large" my.cnf example configuration file
and had a slight speedup it still took longer than a few hours so I
interrupted.
What indexes do you have?
Following to hints from the helpful inhabitants of #bacula on
irc.freenode.net I ran a "dbcheck" searching for orphaned rows. Voila, my
row count decreased from 21 million to 3 million. I even needed two runs
because dbcheck seemed to have an upper limit of 10 million entries to
delete. :)
That won't help, but proper indexing should speed things up.
AB
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
