[Gluster-users] very bad performance on small files

[Jacob Shucart]

For web hosting it is best to put user generated content(images, etc) on
Gluster but to leave application files like PHP files on the local disk.
This is because a single application file request could result in 20 other
file requests since applications like PHP use includes/inherits, etc.
This kind of thing is fine on local disks, but when you're talking about a
distributed filesystem the network latency starts to add up since 1
request to the web server results in a bunch of file requests.

-----Original Message-----
From: gluster-users-bounces at gluster.org
[mailto:gluster-users-bounces at gluster.org] On Behalf Of Max Ivanov
Sent: Friday, January 14, 2011 6:09 AM
To: Burnash, James
Cc: gluster-users at gluster.org
Subject: Re: [Gluster-users] very bad performance on small files

> Gluster - and in fact most (all?) parallel filesystems are optimized for
very large files. That being the case, small files are not retrieved as
efficiently, and result in a larger number of file operations in total
because there are a fixed number for each file accessed.


Which makes glusterfs perfomance unacceptable for web hosting purposes =(
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users