This depends on the filesystem used, but I would recomend you to
organized them by year. Now you
have few hundred articles, two or three years later it might be 1000,
and reorganize it then would be
much harder then to create the directories now.
Monty wrote:
This is a more general server
I'm storing somewhere over 100,000 separate articles on my site, using
ht://dig to index them. They're organized as //MM/nn. No performance
problems to speak of on a pretty popular non-commercial site (2-3
pageviews/sec, 24x7) whether they just browse through the directories or or
use
IMHO it depends on the O/S and filesystem. For example, there's an fs
for Linux called Reiser FS that uses semibalanced binary trees to speed
up file organization, so that even with high file counts you shouldn't
experience major delays. Some other filesystems have hard limits on the
number of
I read in here once or twice that it's worth worrying about at the 1000's
mark, not 100's.
However, hashing them into years (/2002/), or categories (/sports/), or
alphabetically (/a/, /b/, /c/), or by author might prove beneficial froma
content management point of view. Then logical end choice
Why not store them in a database with one php script selecting them?
Monty wrote:
This is a more general server question: I know that having a large number of
files in one folder can slow down a web server, but, how many would it take
for this to be a problem? Wondering if I should store all
)
Newsgroups: php.general
Date: Fri, 25 Oct 2002 00:55:48 -0400
To: Monty [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP] How many is too many?
Why not store them in a database with one php script selecting them?
Monty wrote:
This is a more general server question: I know
6 matches
Mail list logo
