Re: [HACKERS] poor performance with Context Switch Storm at TPC-W.

2006-07-20 Thread Katsuhiko Okano
"Jim C. Nasby" wrote: > If you haven't changed checkpoint timeout, this drop-off every 4-6 > minutes indicates that you need to make the bgwriter more aggressive. I'll say to a customer when proposing and explaining. Thank you for the information. Regards, Katsuhiko Okano okano katsuhiko

Re: [HACKERS] poor performance with Context Switch Storm at TPC-W.

2006-07-19 Thread Jim C. Nasby
On Fri, Jul 14, 2006 at 02:58:36PM +0900, Katsuhiko Okano wrote: > NOT occurrence of CSStorm. The value of WIPS was about 400. > (but the value of WIPS fell about to 320 at intervals of 4 to 6 minutes.) If you haven't changed checkpoint timeout, this drop-off every 4-6 minutes indicates that you n

Re: CSStorm occurred again by postgreSQL8.2. (Re: [HACKERS] poor performance with Context Switch Storm at TPC-W.)

2006-07-19 Thread Katsuhiko Okano
"Tom Lane <[EMAIL PROTECTED]>" wrote: > Katsuhiko Okano <[EMAIL PROTECTED]> writes: > > It does not solve, even if it increases the number of NUM_SUBTRANS_BUFFERS. > > The problem was only postponed. > > Can you provide a reproducible test case for this? Seven machines are required in order to pe

Re: CSStorm occurred again by postgreSQL8.2. (Re: [HACKERS] poor performance with Context Switch Storm at TPC-W.)

2006-07-18 Thread Tom Lane
Katsuhiko Okano <[EMAIL PROTECTED]> writes: > It does not solve, even if it increases the number of NUM_SUBTRANS_BUFFERS. > The problem was only postponed. Can you provide a reproducible test case for this? regards, tom lane ---(end of broadcast)--

CSStorm occurred again by postgreSQL8.2. (Re: [HACKERS] poor performance with Context Switch Storm at TPC-W.)

2006-07-18 Thread Katsuhiko Okano
Katsuhiko Okano wrote: > By PostgreSQL8.2, NUM_SUBTRANS_BUFFERS was changed into 128 > and recompile and measured again. > NOT occurrence of CSStorm. The value of WIPS was about 400. measured again. not occurrence when measured for 30 minutes. but occurrence when measured for 3 hours, and 1 hour a

Re: [HACKERS] poor performance with Context Switch Storm at TPC-W.

2006-07-13 Thread Katsuhiko Okano
Hi. Alvaro Herrera wrote: > Katsuhiko Okano wrote: > > > I suspected conflict of BufMappingLock. > > but, collected results are seen, > > occurrence of CSStorm and the increase of BufMappingLock counts > > seem not to correspond. > > Instead, SubtransControlLock and SubTrans were increasing. >

Re: [HACKERS] poor performance with Context Switch Storm at TPC-W.

2006-07-11 Thread Katsuhiko Okano
hello. > Do you have bgwriter on and what's the parameters? I read a theory somewhere > that bgwriter scan a large portion of memory and cause L1/L2 thrushing, so > with HT on, the other backends sharing the physical processor with it also > get thrashed ... So try to turn bgwriter off or turn HT

Re: [HACKERS] poor performance with Context Switch Storm at TPC-W.

2006-07-11 Thread Josh Berkus
Katsuhiko, Have you tried turning HT off? HT is not generally considered (even by Intel) a good idea for database appplications. --Josh ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose

Re: [HACKERS] poor performance with Context Switch Storm at TPC-W.

2006-07-11 Thread Alvaro Herrera
Katsuhiko Okano wrote: > I suspected conflict of BufMappingLock. > but, collected results are seen, > occurrence of CSStorm and the increase of BufMappingLock counts > seem not to correspond. > Instead, SubtransControlLock and SubTrans were increasing. > I do not understand what in the cause of CS

Re: [HACKERS] poor performance with Context Switch Storm at TPC-W.

2006-07-11 Thread Qingqing Zhou
"Katsuhiko Okano" <[EMAIL PROTECTED]> wrote > > The problem has occurred in my customer. > poor performance with Context Switch Storm occurred > with the following composition. > Usually, CS is about 5000, WIPS=360. > when CSStorm occurrence, CS is about 10, WIPS=60 or less. > > Intel Xeon 3.0