From: | Jim Nasby <jnasby(at)pervasive(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Transactions per second |
Date: | 2006-05-04 22:23:33 |
Message-ID: | 925ED229-00D7-494E-B4F0-A6D52295031B@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I often find myself wanting to know how many transactions per second
a database is committing to disk, as well as how many queries per
second it's processing. While Larry's busy making stats changes, I'd
like to propose a few more counters:
Number of commits: Ideally, this would only count transactions that
actually modify data
Number of statements: Simply, how many statements have been executed
Number of DML statements: how many insert/update/delete statements
executed.
For the last two, it would be ideal if they counted statements that
were executed inside of a function.
Having these counters would make it easier to determine what kind of
workload a server is actually handling. It's currently possible to
determine transactions over a time period, but the process is rather
convoluted and doesn't differentiate between transactions that modify
data and those that don't.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-05-05 02:04:53 | Re: Is a SERIAL column a "black box", or not? |
Previous Message | Tom Lane | 2006-05-04 22:07:26 | Re: Semi-undocumented functions in libpq |