Re: testing ProcArrayLock patches
От | Robert Haas |
---|---|
Тема | Re: testing ProcArrayLock patches |
Дата | |
Msg-id | CA+TgmobgjO8hh9M5agaV=+i6zeJ1yVd2L9TaXyHjwLWmcHeBcQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: testing ProcArrayLock patches ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: testing ProcArrayLock patches
Re: testing ProcArrayLock patches |
Список | pgsql-hackers |
On Fri, Nov 18, 2011 at 2:05 PM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote: > Robert Haas <robertmhaas@gmail.com> wrote: >> Any chance you can run oprofile (on either branch, don't really >> care) against the 32 client test and post the results? > > [ oprofile results ] Hmm. That looks a lot like a profile with no lock contention at all. Since I see XLogInsert in there, I assume this must be a pgbench write test on unlogged tables? How close am I? I was actually thinking it would be interesting to oprofile the read-only test; see if we can figure out where those slowdowns are coming from. > Two runs: > > tps = 21946.961196 (including connections establishing) > tps = 22911.873227 (including connections establishing) > > For write transactions, that seems pretty respectable. Very. What do you get without the patch? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: