I have no clue how big the files are, but you might want to store them
in a database. That can speed up things, but don't ask me how much ;)
Tijnema
no dude, while database are convenient, files systems are faster, I mean
thats what they were designed for, serving files.
For lots of files I
clive wrote:
I have no clue how big the files are, but you might want to store them
in a database. That can speed up things, but don't ask me how much ;)
Tijnema
no dude, while database are convenient, files systems are faster, I mean
thats what they were designed for, serving files.
On 6/18/07, Colin Guthrie [EMAIL PROTECTED] wrote:
clive wrote:
I have no clue how big the files are, but you might want to store them
in a database. That can speed up things, but don't ask me how much ;)
Tijnema
no dude, while database are convenient, files systems are faster, I mean
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
On 6/18/07, Colin Guthrie [EMAIL PROTECTED] wrote:
clive wrote:
I have no clue how big the files are, but you might want to store them
in a database. That can speed up things, but don't ask me how much ;)
Tijnema
no dude, while
On 6/18/07, Tijnema [EMAIL PROTECTED] wrote:
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
On 6/18/07, Colin Guthrie [EMAIL PROTECTED] wrote:
clive wrote:
I have no clue how big the files are, but you might want to store them
in a database. That can speed up things, but don't ask
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
On 6/18/07, Tijnema [EMAIL PROTECTED] wrote:
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
On 6/18/07, Colin Guthrie [EMAIL PROTECTED] wrote:
clive wrote:
I have no clue how big the files are, but you might want to store them
On 6/18/07, Tijnema [EMAIL PROTECTED] wrote:
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
On 6/18/07, Tijnema [EMAIL PROTECTED] wrote:
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
On 6/18/07, Colin Guthrie [EMAIL PROTECTED] wrote:
clive wrote:
I have no clue how big
On Mon, 2007-06-18 at 11:25 -0400, Daniel Brown wrote:
On 6/18/07, Tijnema [EMAIL PROTECTED] wrote:
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
Referring to one of my earlier posts in this thread, as a
refresher, database information is stored in files. So to store files
Daniel Brown wrote:
On 6/18/07, Tijnema [EMAIL PROTECTED] wrote:
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
On 6/18/07, Tijnema [EMAIL PROTECTED] wrote:
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
On 6/18/07, Colin Guthrie [EMAIL PROTECTED] wrote:
clive wrote:
I
On Mon, 2007-06-18 at 08:41 -0700, Jim Lucas wrote:
Daniel Brown wrote:
On 6/18/07, Tijnema [EMAIL PROTECTED] wrote:
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
On 6/18/07, Tijnema [EMAIL PROTECTED] wrote:
On 6/18/07, Daniel Brown [EMAIL PROTECTED] wrote:
On 6/18/07, Colin
For everyone who advised me to beware the inode, allow me to
forward what the Rackspace admins told me. This is Greek to me, and
I'm hoping one of you can translate. All I understood was where he
said I appear to have more than enough. Yes?
---snip---
All of your slices on the disk are
On 6/17/07, Brian Dunning [EMAIL PROTECTED] wrote:
For everyone who advised me to beware the inode, allow me to
forward what the Rackspace admins told me. This is Greek to me, and
I'm hoping one of you can translate. All I understood was where he
said I appear to have more than enough. Yes?
Server is running Linux, and PHP is constantly creating and modifying
images in a directory. Apache is constantly serving these same
images. There are about 250,000 of them in the same directory. Seems
to be running OK, no problematic CPU load, but I'm wondering if
anyone knows whether I'm
[snip]
Server is running Linux, and PHP is constantly creating and modifying
images in a directory. Apache is constantly serving these same
images. There are about 250,000 of them in the same directory. Seems
to be running OK, no problematic CPU load, but I'm wondering if
anyone knows
6/15/07, Jay Blanchard [EMAIL PROTECTED] wrote:
[snip]
Server is running Linux, and PHP is constantly creating and modifying
images in a directory. Apache is constantly serving these same
images. There are about 250,000 of them in the same directory. Seems
to be running OK, no problematic CPU
On Saturday 16 June 2007 02:51, Daniel Brown wrote:
And remember, the fact that they're all
in one directory doesn't matter at all to the system, as directories,
folders, et cetera, are just representations for human readability and
organization. In fact, those files reside on several
Thanks for the replies but I'm not sure I know what to do with them.
Is the problem with the number of files, or is the problem with the
activity? Can you dumb down your answers at all for me? :)
On Jun 15, 2007, at 11:51 AM, Daniel Brown wrote:
6/15/07, Jay Blanchard [EMAIL PROTECTED]
On 6/15/07, Crayon Shin Chan [EMAIL PROTECTED] wrote:
On Saturday 16 June 2007 02:51, Daniel Brown wrote:
And remember, the fact that they're all
in one directory doesn't matter at all to the system, as directories,
folders, et cetera, are just representations for human readability and
I can easily break it up into 100 subdirectories, 2500 files in each,
would that be good insurance against problems?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
[snip]
I can easily break it up into 100 subdirectories, 2500 files in each,
would that be good insurance against problems?
[/snip]
As someone mentioned, directories are just a human convenience. Each
file will have an inode and is identified by an inode number in the file
system where it
On 6/15/07, Brian Dunning [EMAIL PROTECTED] wrote:
I can easily break it up into 100 subdirectories, 2500 files in each,
would that be good insurance against problems?
I have no clue how big the files are, but you might want to store them
in a database. That can speed up things, but don't ask
On 6/15/07, Brian Dunning [EMAIL PROTECTED] wrote:
Thanks for the replies but I'm not sure I know what to do with them.
Is the problem with the number of files, or is the problem with the
activity? Can you dumb down your answers at all for me? :)
On Jun 15, 2007, at 11:51 AM, Daniel Brown
On 6/15/07, Jay Blanchard [EMAIL PROTECTED] wrote:
[snip]
I can easily break it up into 100 subdirectories, 2500 files in each,
would that be good insurance against problems?
[/snip]
As someone mentioned, directories are just a human convenience. Each
file will have an inode and is identified
]
To: php-general@lists.php.net
Sent: Friday, June 15, 2007 9:38 PM
Subject: Re: [PHP] OK to have many files in one folder?
Thanks for the replies but I'm not sure I know what to do with them. Is
the problem with the number of files, or is the problem with the
activity? Can you dumb down your
On Saturday 16 June 2007 03:47, Daniel Brown wrote:
Once again, this doesn't matter so much for per-directory (though
listing will take longer, as I think I mentioned) as it does the
filesystem mount.
Several years ago, having say 3000+ files in single directory on ext2
would mean that
Jay Blanchard wrote:
[snip]
Server is running Linux, and PHP is constantly creating and modifying
images in a directory. Apache is constantly serving these same
images. There are about 250,000 of them in the same directory. Seems
to be running OK, no problematic CPU load, but I'm wondering
[snip]
Two words. Beware the inode.
^^ ^^^ ^
1 23
Here endeth the lesson.
[/snip]
Can I get an Admin brotha'!?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
27 matches
Mail list logo
