[Gluster-users] (no subject)
Larry Bates
larry.bates at vitalesafe.com
Tue May 4 19:27:50 UTC 2010
I thought I would at least chime in here about read performance on small files.
Seems to me that this problem should more likely be solved with Squid. Nginx, or
some caching software. If I'm understanding the problem, the files are mostly
read-only .html files which would react well to being cached by a well
configured cache that shouldn't be too hard to set up. Hope info helps in some
way.
Larry Bates
vitalEsafe, Inc.
------------------------------
Message: 3
Date: Tue, 4 May 2010 14:24:44 -0400
From: "Burnash, James" <jburnash at knight.com>
Subject: Re: [Gluster-users] Performance Issue with Webserver
To: "gluster-users at gluster.org" <gluster-users at gluster.org>
Message-ID:
<9AD565C4A8561349B7227B79DDB988733179EA485D at EXCHANGE3.global.knight.com>
Content-Type: text/plain; charset="us-ascii"
Hi Jenn,
You may not have seen the posts, but small files do not, as a general rule, do
well on parallel file systems. There are numerous posts on this subject on this
list concerning this subject, and the Gluster developers have devoted a good bit
of energy into trying to address this, but ... this is not a general purpose
file system. It is designed to be efficient with large(r) file sizes.
Throughput is (hopefully) limited by the bandwidth available - but latency comes
is a factor as well in determining throughput.
Others on this list can give you much better details.
James
-----Original Message-----
From: gluster-users-bounces at gluster.org
[mailto:gluster-users-bounces at gluster.org] On Behalf Of Jenn Fountain
Sent: Tuesday, May 04, 2010 1:32 PM
To: gluster-users at gluster.org
Subject: [Gluster-users] Performance Issue with Webserver
We are running our webapp on a gluster mount. We are finding that performance
is a lot slower than local disk. We expected it to be slower but not this much
slower. So, I am looking to you for some guidance on what to do. IE: Not run
off the gluster mount or change config settings, etc.
Here are some numbers on performance:
Gluster Mount html:
Document Path: /tmp/test.html
Document Length: 17 bytes
Concurrency Level: 1
Time taken for tests: 0.269 seconds
Complete requests: 1
Failed requests: 0
Write errors: 0
Total transferred: 302 bytes
HTML transferred: 17 bytes
Requests per second: 3.72 [#/sec] (mean)
Time per request: 268.621 [ms] (mean)
Time per request: 268.621 [ms] (mean, across all concurrent requests)
Transfer rate: 1.10 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 16 16 0.0 16 16
Processing: 253 253 0.0 253 253
Waiting: 253 253 0.0 253 253
Total: 269 269 0.0 269 269
Local disk html:
Document Path: /tmp2/test.html
Document Length: 16 bytes
Concurrency Level: 1
Time taken for tests: 0.035 seconds
Complete requests: 1
Failed requests: 0
Write errors: 0
Total transferred: 301 bytes
HTML transferred: 16 bytes
Requests per second: 28.24 [#/sec] (mean)
Time per request: 35.409 [ms] (mean)
Time per request: 35.409 [ms] (mean, across all concurrent requests)
Transfer rate: 8.30 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 20 20 0.0 20 20
Processing: 16 16 0.0 16 16
Waiting: 16 16 0.0 16 16
Total: 35 35 0.0 35 35
More information about the Gluster-users
mailing list