On Wed, 26 Oct 2005, Russell Howe wrote:
Check to see if Postgres is issuing an fsync() after every operation
or not, and then decide if you need it to.
If you can disable that, things should get a *LOT* faster. I posted
a link to some Postgresql performance tuning documents a while back
- they're linked to from the postgres website too.
At the risk of being somewhat off-topic, I'll add that the same is
true of SQLite. In SQLite 2.8, setting the default_synchronous flag to
OFF will speed things up markedly:
echo 'PRAGMA default_synchronous=0;' | sqlite bacula.db
The danger is that a system crash can easily result in a wholly
corrupted database. In fact, the SQLite developers have removed this
functionality from version 3, calling it "dangerous." Make sure you
read the documentation to understand the dangers:
http://www.sqlite.org/pragma.html
The upside is that attribute spooling that used to take a couple days
is now done in a few hours. My weekly full backups used to take from
Friday night until Monday night; now they start Saturday evening and
are finished about the time I get my Sunday-morning coffee.
--
Paul Heinlein <> [EMAIL PROTECTED] <> www.madboa.com
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
