Обсуждение: How to build with bigger WAL segment file?
Since I have a database with a frequent and huge update batch, the WAL segment file number is about 130. I suspect these files management during the update is hurting performance. Is it likely? I'm using Fedora Core 3 and checkpoint_segments is set to 64. To overcome this I'm considering to make the WAL segment files bigger. The segment file default size is 16 MB. How to build from the source rpm to have bigger files, say 128 MB? Regards, Clodoaldo
2006/6/19, Clodoaldo Pinto <clodoaldo.pinto@gmail.com>: > Since I have a database with a frequent and huge update batch, the WAL > segment file number is about 130. I suspect these files management > during the update is hurting performance. Is it likely? I'm using > Fedora Core 3 and checkpoint_segments is set to 64. > > To overcome this I'm considering to make the WAL segment files bigger. > The segment file default size is 16 MB. How to build from the source > rpm to have bigger files, say 128 MB? > I found it in src/include/pg_config_manual.h: /* * XLOG_SEG_SIZE is the size of a single WAL file. This must be a power of 2 * and larger than BLCKSZ (preferably, a great deal larger than BLCKSZ). * * Changing XLOG_SEG_SIZE requires an initdb. */ #define XLOG_SEG_SIZE (16*1024*1024)
On Jun 19, 2006, at 4:10 PM, Clodoaldo Pinto wrote: > 2006/6/19, Clodoaldo Pinto <clodoaldo.pinto@gmail.com>: >> Since I have a database with a frequent and huge update batch, the >> WAL >> segment file number is about 130. I suspect these files management >> during the update is hurting performance. Is it likely? I'm using >> Fedora Core 3 and checkpoint_segments is set to 64. >> >> To overcome this I'm considering to make the WAL segment files >> bigger. >> The segment file default size is 16 MB. How to build from the source >> rpm to have bigger files, say 128 MB? >> > > I found it in src/include/pg_config_manual.h: BTW, someone (Mark Wong?) recently posted some performance testing results from upping XLOG_SEG_SIZE... take a look in the archives. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461