Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 922679FB476 for ; Fri, 4 May 2007 14:01:51 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 12797-04 for ; Fri, 4 May 2007 14:01:48 -0300 (ADT) X-Greylist: delayed 00:21:11.410428 by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 879C89FB4FC for ; Fri, 4 May 2007 14:01:39 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from mail.laliluna.com (mail.laliluna.com [85.190.26.55]) by svr4.postgresql.org (Postfix) with ESMTP id D72FC5AF8A7 for ; Fri, 4 May 2007 16:40:26 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by mail.laliluna.com (Postfix) with ESMTP id DACF85F8097 for ; Fri, 4 May 2007 18:40:13 +0200 (CEST) Received: from mail.laliluna.com ([85.190.26.55]) by localhost (asterix.laliluna.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x5Qb3B1GJh6O for ; Fri, 4 May 2007 18:40:13 +0200 (CEST) Received: from [192.168.1.100] (p54b2c87c.dip.t-dialin.net [84.178.200.124]) by mail.laliluna.com (Postfix) with ESMTP id A991D5F808A for ; Fri, 4 May 2007 18:40:13 +0200 (CEST) Message-ID: <463B61ED.20409@laliluna.de> Date: Fri, 04 May 2007 18:40:13 +0200 From: Sebastian Hennebrueder User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 Cc: pgsql-performance@postgresql.org Subject: Re: Feature Request --- was: PostgreSQL Performance Tuning References: <200704271059.50265.josh@agliodbs.com> <200705010923.47951.josh@agliodbs.com> <4637CFF7.7020000@mochima.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 200705/49 X-Sequence-Number: 24439 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