Re: [HACKERS] Heh, the disappearing problem!
От | Karl Denninger |
---|---|
Тема | Re: [HACKERS] Heh, the disappearing problem! |
Дата | |
Msg-id | 19980309221555.63948@mcs.net обсуждение исходный текст |
Ответ на | Re: [HACKERS] Heh, the disappearing problem! (Bruce Momjian <maillist@candle.pha.pa.us>) |
Ответы |
Re: [HACKERS] Heh, the disappearing problem!
Re: [HACKERS] Heh, the disappearing problem! |
Список | pgsql-hackers |
On Mon, Mar 09, 1998 at 11:05:49PM -0500, Bruce Momjian wrote: > > I've seen this same kind of behavior in a few other places as well; in > > places where you are doing reads and writes in a mixed environment (ie: read > > something, write something (typically in a different table) based on what > > you read) performance of 6.3 has gone in the toilet. Update jobs that used > > to run in tens of seconds are requiring several minutes to complete now. > > > > And again, we're not seeing much disk I/O during this period - but we *ARE* > > seeing a hell of a lot of CPU activity, almost all in user mode. > > OK, how about using postgres -t option or profiling to get the function > using so much cpu? This may help us tell where the problem lies. Does > anyone else see such problems? All other reports I hear was that 6.3 > was faster. Docs on this somewhere? I'll be happy to profile it if I can figure out how! :-) -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost
В списке pgsql-hackers по дате отправления: