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 you make will
depend on your site, and how people use it.
For the amount of articles you're talking about, you'd definitely only need
one level of hashing.
on 25/10/02 2:40 PM, Monty ([EMAIL PROTECTED]) 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 articles for a
> content site in one big 'articles' folder with each article having it's own
> folder within (/articles/article_id/), or if I should organize them by year
> then article name (/articles/2002/article_id). The site will only produce a
> few hundred articles a year. I'd like the keep the file structure shallow
> and simple if possible, but, if it could potentially slow the server down by
> putting so many folder in one I'll split them up more.
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php