[Bacula-users] abysmal database write performance

[<bo...@in...>]

Hi there,

currently we are using postgresql 8.0.6 (default configuration) under 
FC4 for the catalog (with bacula 1.38.5).
I decided to spool the attributes of our jobs before storing in the 
database because of a bad performance. Some jobs are having a lot of 
files and so the attribute spool files are quite big (about 800 MB to 
1.6 GB).
So far so good. But storing the attributes in the database takes a very 
long time. The 1.6 GB spool needs 10 hours!
During this time the CPUs and discs are mostly idle. (The process status 
of the postmaster says: uninterruptible sleep.)

I tried to "tune" postgreSQL by modifying some settings in the 
postgresql.conf:
   shared_buffers = 2048
   wal_buffers = 64
   max_connections = 40
Nevertheless, it doesn't help. :-(

[The biggest job has ~4.500.000 files at the moment. Over all the 
"filename" table has about 2.000.000 rows, the "file" table has 
19.000.000 rows. Not too much I think.
The recommended indexes were created. But I'm not happy about the 
performance.
I'm afraid to disable fsync for postgresql. (Should this be the solution?)

Any ideas?

Thanks.


Jens Boettge