X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id A67919DD647 for ; Fri, 2 Dec 2005 03:49:56 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 81495-01 for ; Fri, 2 Dec 2005 03:49:53 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from cliff.cs.toronto.edu (cliff.cs.toronto.edu [128.100.3.120]) by postgresql.org (Postfix) with ESMTP id DE8859DD61B for ; Fri, 2 Dec 2005 03:49:53 -0400 (AST) Received: from eon.cs (eon.cs.toronto.edu [128.100.3.15]) by cliff.cs.toronto.edu (Postfix) with ESMTP id B4BD45FD08; Fri, 2 Dec 2005 02:49:52 -0500 (EST) Received: by eon.cs (Postfix, from userid 1300) id 2C074805; Fri, 2 Dec 2005 02:49:53 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by eon.cs (Postfix) with ESMTP id 22933583; Fri, 2 Dec 2005 02:49:53 -0500 (EST) Date: Fri, 2 Dec 2005 02:49:53 -0500 (EST) From: Qingqing Zhou X-X-Sender: zhouqq@eon.cs To: David Lang Cc: pgsql-performance@postgresql.org Subject: Re: filesystem performance with lots of files In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.359 required=5 tests=[AWL=-0.120, DNS_FROM_RFC_ABUSE=0.479] X-Spam-Score: 0.359 X-Spam-Level: X-Archive-Number: 200512/55 X-Sequence-Number: 15876 On Fri, 2 Dec 2005, David Lang wrote: > > I don't have all the numbers readily available (and I didn't do all the > tests on every filesystem), but I found that even with only 1000 > files/directory ext3 had some problems, and if you enabled dir_hash some > functions would speed up, but writing lots of files would just collapse > (that was the 80 min run) > Interesting. I would suggest test small number but bigger file would be better if the target is for database performance comparison. By small number, I mean 10^2 - 10^3; By bigger, I mean file size from 8k to 1G (PostgreSQL data file is at most this size under normal installation). Let's take TPCC as an example, if we get a TPCC database of 500 files, each one is at most 1G (PostgreSQL has this feature/limit in ordinary installation), then this will give us a 500G database, which is big enough for your current configuration. Regards, Qingqing