From: Sebastian Hennebrueder <usenet@laliluna.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: Feature Request --- was: PostgreSQL Performance Tuning
Date: Fri, 04 May 2007 18:40:13 +0200
Message-ID: <463B61ED.20409@laliluna.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0705011647360.12033@asgard.lang.hm>
References: <OFC96167D5.6BB63AC2-ON652572C9.003B5263-652572C9.003E4142@lntinfotech.com>
<200704271059.50265.josh@agliodbs.com>
<Pine.GSO.4.64.0704292241270.1296@westnet.com>
<200705010923.47951.josh@agliodbs.com>
<4637CFF7.7020000@mochima.com>
<Pine.LNX.4.64.0705011647360.12033@asgard.lang.hm>
david@lang.hm schrieb:
> On Tue, 1 May 2007, Carlos Moreno wrote:
>
>>> large problem from a slog perspective; there is no standard way even
>>> within Linux to describe CPUs, for example. Collecting available disk
>>> space information is even worse. So I'd like some help on this
>>> portion.
>>>
>>
>> Quite likely, naiveness follows... But, aren't things like
>> /proc/cpuinfo ,
>> /proc/meminfo, /proc/partitions / /proc/diskstats standard, at the very
>> least across Linux distros? I'm not familiar with BSD or other Unix
>> flavours, but I would expect these (or their equivalent) to exist in
>> those,
>> no?
>>
>> Am I just being naive?
>
> unfortunantly yes.
>
> across different linux distros they are fairly standard (however
> different kernel versions will change them)
>
> however different kernels need drasticly different tools to get the
> info from them.
>
> David Lang
>
Before inventing a hyper tool, we might consider to provide 3-5 example
szenarios for common hardware configurations. This consumes less time
and be discussed and defined in a couple of days. This is of course not
the correct option for a brandnew 20 spindle Sata 10.000 Raid 10 system
but these are probably not the target for default configurations.
If we carefully document these szenario they would we a great help for
people having some hardware "between" the szenarios.
Sebastian Hennebrueder
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: usenet@laliluna.de
Subject: Re: Feature Request --- was: PostgreSQL Performance Tuning
In-Reply-To: <463B61ED.20409@laliluna.de>
* 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