Re: [HACKERS] RE: Re: [ADMIN] v7.1b4 bad performance

2001-02-27 Thread Vadim Mikheev
> So 7.0.3 is twice as fast only with fsync off. Are there FK updates/deletes in pgbench' tests? Remember how SELECT FOR UPDATE in FK triggers affects performance... Also, 5 clients is small number. Vadim P.S. Sorry for delays with my replies - internet connection is pain here: it takes 5-10 min

Re: [HACKERS] RE: Re: [ADMIN] v7.1b4 bad performance

2001-02-25 Thread Lincoln Yeoh
Oops I screwed up again. :) I was actually right the first time my postgresql 7.0.3 was running with fsync off. Due to my weird results I searched more thoroughly and found my 7.0.3's pg_options had a nofsync=1. So 7.0.3 is twice as fast only with fsync off. 7.1beta4 snapshot - fsync. ./pgben

Re: [HACKERS] RE: Re: [ADMIN] v7.1b4 bad performance

2001-02-23 Thread Vadim Mikheev
> It may be that WAL has changed the rollback > time-characteristics to worse than pre-wal ? Nothing changed ... yet. And in future rollbacks of read-only transactions will be as fast as now, anyway. > > So my guess is that the 7.1 updates (with default > > fsync) are significantly slower than 7

Re: [HACKERS] RE: Re: [ADMIN] v7.1b4 bad performance

2001-02-23 Thread Vadim Mikheev
> > > It may be that WAL has changed the rollback > > > time-characteristics to worse than pre-wal ? > > > > Nothing changed ... yet. And in future rollbacks > > of read-only transactions will be as fast as now, > > anyway. > > What about rollbacks of a bunch uf inserts/updates/deletes? > > I rem

Re: [HACKERS] RE: Re: [ADMIN] v7.1b4 bad performance

2001-02-23 Thread Lincoln Yeoh
At 09:40 AM 22-02-2001 -0500, Vadim Mikheev wrote: >> It may be that WAL has changed the rollback >> time-characteristics to worse than pre-wal ? > >Nothing changed ... yet. And in future rollbacks >of read-only transactions will be as fast as now, >anyway. The rollbacks are ok for me at least -

Re: [HACKERS] RE: Re: [ADMIN] v7.1b4 bad performance

2001-02-23 Thread Hannu Krosing
Vadim Mikheev wrote: >> Should this kind of usage be replaced in the future by >> having backend id as a key and then doing delete by that >> key in the end ? > > > Isn't it what we have right now? I meant doing it at the application level, not what backend does internally. Like we are supp

Re: [HACKERS] RE: Re: [ADMIN] v7.1b4 bad performance

2001-02-22 Thread Hannu Krosing
Vadim Mikheev wrote: > > > It may be that WAL has changed the rollback > > time-characteristics to worse than pre-wal ? > > Nothing changed ... yet. And in future rollbacks > of read-only transactions will be as fast as now, > anyway. What about rollbacks of a bunch uf inserts/updates/deletes?

Re: [HACKERS] RE: Re: [ADMIN] v7.1b4 bad performance

2001-02-22 Thread Hannu Krosing
Lincoln Yeoh wrote: > > Just another data point. > > I downloaded a snapshot yesterday - Changelogs dated Feb 20 17:02 > > It's significantly slower than "7.0.3 with fsync off" for one of my webapps. > > 7.0.3 with fsync off gets me about 55 hits per sec max (however it's > interesting that th

[HACKERS] RE: Re: [ADMIN] v7.1b4 bad performance

2001-02-21 Thread Lincoln Yeoh
Just another data point. I downloaded a snapshot yesterday - Changelogs dated Feb 20 17:02 It's significantly slower than "7.0.3 with fsync off" for one of my webapps. 7.0.3 with fsync off gets me about 55 hits per sec max (however it's interesting that the speed keeps dropping with continued t

[HACKERS] RE: Re: [ADMIN] v7.1b4 bad performance

2001-02-21 Thread Lincoln Yeoh
Oops. I rechecked the start up script, and the 7.0.3 doesn't have fsync off or whatever. Dunno why I thought it was on (heh maybe because it was a lot faster than 6.5.3!). Hmm, this means 7.0.3 is quite fast... Cheerio, Link.