> 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. :-(
What kind of hardware are you on? 2048 shared buffers is very low for a lot of systems. I'd bump it up a bit (but not too far! FOr example, I use about 25,000 for a system with 2Gb RAM) Is your effective_cache_size properly set? Setting of full_page_writes? [that may be a 8.1 setting, can't remember, but it makes a huge difference if you have an I/O system yuo acn trust] work_mem, maintenance_work_mem? checkpoint_segments? Most improtantly, what's your I/O system? Writeback cache? WAL on separate spindles? Type of disks (IDE/SATA/SCSI?) State "uninterruptible sleep" often means it's blocking on I/O. Unless you have a hardware problem somewhere. > [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. The indexes will generally *hurt* your insert performance, which is what Bacula mainly needs during writes. I'll speed up restore operations, but there's the cost. > I'm afraid to disable fsync for postgresql. (Should this be > the solution?) You can disable it, but if your system crashes (hardware or OS), you will need to recover your catalog bacukp. Always do that even if it looks ok - it'll come back to bite you. In general, I would definitly not recommend running with fsync off, it's very dangerous (but then I'm a database guy, so what else would you expect..). //Magnus ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
