pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Carlos Moreno <moreno_pg@mochima.com>
To: pgsql-performance@postgresql.org
Subject: Re: Feature Request --- was: PostgreSQL Performance Tuning
Date: Thu, 03 May 2007 17:06:30 -0400
Message-ID: <463A4ED6.2040907@mochima.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705031314310.26172@asgard.lang.hm>
References: <OFC96167D5.6BB63AC2-ON652572C9.003B5263-652572C9.003E4142@lntinfotech.com>
	<200705010923.47951.josh@agliodbs.com>
	<Pine.GSO.4.64.0705012154380.24215@westnet.com>
	<200705031221.56226.josh@agliodbs.com>
	<Pine.LNX.4.64.0705031314310.26172@asgard.lang.hm>


>> CPUs, 32/64bit, or clock speeds.   So any attempt to determine "how 
>> fast"
>> a CPU is, even on a 1-5 scale, requires matching against a database of
>> regexes which would have to be kept updated.
>>
>> And let's not even get started on Windows.
>
> I think the only sane way to try and find the cpu speed is to just do 
> a busy loop of some sort (ideally something that somewhat resembles 
> the main code) and see how long it takes. you may have to do this a 
> few times until you get a loop that takes long enough (a few seconds) 
> on a fast processor

I was going to suggest just that (but then was afraid that again I may have
been just being naive) --- I can't remember the exact name, but I remember
using (on some Linux flavor) an API call that fills a struct with data 
on the
resource usage for the process, including CPU time;  I assume measured
with precision  (that is, immune to issues of other applications running
simultaneously, or other random events causing the measurement to be
polluted by random noise).

As for 32/64 bit --- doesn't PG already know that information?  I mean,
./configure does gather that information --- does it not?

Carlos
--




view thread (53+ messages)  latest in thread

Message-ID: <463A4ED6.2040907@mochima.com>
Permalink:  ../463A4ED6.2040907@mochima.com/
Also on:    postgresql.org/message-id/463A4ED6.2040907@mochima.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: moreno_pg@mochima.com
  Subject: Re: Feature Request --- was: PostgreSQL Performance Tuning
  In-Reply-To: <463A4ED6.2040907@mochima.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox