I'm storing the article text and details in a database, but, all the assets (these articles have lots of photos) need to be organized into folders. So logically I want to create a folder for each article using the article ID number. But I want to be sure if I have within the Article folder about 700 other folders that contain all the assets for every article that that won't slow down the server. This site will not be visited by millions necessarily, but, I still want to be sure I'm setting up the file system as efficiently as possible.
Thanks! > From: [EMAIL PROTECTED] (Leif K-Brooks) > 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 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. >> >> Thanks! >> -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
