Horton

Re: pgbench cpu overhead (was Re: lazy vxid locks, v1)

Itagaki Takahiro <itagaki.takahiro@gmail.com>

View thread
From: Itagaki Takahiro <itagaki.takahiro@gmail.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>, pgsql-hackers@postgresql.org, Robert Haas <robertmhaas@gmail.com>
Date: 2011-06-14T01:46:20Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Avoid extra system calls to block SIGPIPE if the platform provides either

On Tue, Jun 14, 2011 at 09:27, Jeff Janes <jeff.janes@gmail.com> wrote:
> pgbench sends each query (per connection) and waits for the reply
> before sending another.

We can use -j option to run pgbench in multiple threads to avoid
request starvation. What setting did you use, Stefan?

>> for those curious - the profile for pgbench looks like:
>> samples  %        symbol name
>> 29378    41.9087  doCustom
>> 17502    24.9672  threadRun
>> 7629     10.8830  pg_strcasecmp

If the bench is bottleneck, it would be better to reduce pg_strcasecmp
calls by holding meta command names as integer values of sub-META_COMMAND
instead of string comparison for each loop.

-- 
Itagaki Takahiro