Re: Fwd:Re: client is terrible with large amount of small files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Amukher,

         Even after upgrade to 3.7 small files transfer rate is slow.

Below is the volume info.

Volume Name: integvol1
Type: Replicate
Volume ID: 31793ba4-eeca-462a-a0cd-9adfb281225b
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: integ-gluster1:/srv/sdb2/brick4
Brick2: integ-gluster2:/srv/sdb2/brick4
Options Reconfigured:
server.event-threads: 30
client.event-threads: 30
----

  I understand that for replication it would take some more time, but here its taking more time.


Time taken for git clone in non gluster directory = 25 sec

Time taken for git clone in gluster directory = 14 minutes

Its a huge difference.  Plz let me know any other tuning parameters need to be done.


Regards,
Kamal


    








============ Forwarded Message ============
Date : Thu, 30 Apr 2015 17:14:00 +0530
Subject : Re: [Gluster-users] client is terrible with large amount of small files
============ Forward Message ============

----- Original Message -----
> From: "Atin Mukherjee" <amukherj@xxxxxxxxxx>
> To: "gjprabu" <gjprabu@xxxxxxxxxxxx>
> Sent: Thursday, April 30, 2015 7:37:19 AM
> Subject: Re: client is terrible with large amount of small files
>
>
> On 04/30/2015 03:09 PM, gjprabu wrote:
> > Hi Amukher,
> >
> > How to resolve this issue, till we need to wait for 3.7 release
> > or any work around is there.
> You will have to as this feature is in for 3.7.

My apologies, I didn't realize that MT epoll didn't land in 3.6. If you want to test it out there is an alpha build available:


I wouldn't run this in production until 3.7 is released though. Again sorry for the confusion.

-b

> >
> > RegardsPrabu
> >
> >
> >
> >
> >
> > ---- On Thu, 30 Apr 2015 14:49:46 +0530 Atin
> > Mukherjee&lt;amukherj@xxxxxxxxxx&gt; wrote ----
> >
> >
> >
> > On 04/30/2015 02:32 PM, gjprabu wrote:
> > &gt; Hi bturner,
> > &gt;
> > &gt;
> > &gt; I am getting below error while adding server.event
> > &gt;
> > &gt; gluster v set integvol server.event-threads 3
> > &gt; volume set: failed: option : server.event-threads does not exist
> > &gt; Did you mean server.gid-timeout or ...manage-gids?
> > This option is not available in 3.6, its going to come in 3.7
> >
> > &gt;
> > &gt;
> > &gt; Glusterfs version has been upgraded to 3.6.3
> > &gt; Also os kernel upgraded to 6.6 kernel
> > &gt; Yes two brick are running in KVM and one is physical machine and we
> > are not using thinp.
> > &gt;
> > &gt; Regards
> > &gt; G.J
> > &gt;
> > &gt;
> > &gt;
> > &gt;
> > &gt;
> > &gt; ---- On Thu, 30 Apr 2015 00:37:44 +0530 Ben
> > Turner&amp;lt;bturner@xxxxxxxxxx&amp;gt; wrote ----
> > &gt;
> > &gt; ----- Original Message -----
> > &gt; &amp;gt; From: "gjprabu" &amp;lt;gjprabu@xxxxxxxxxxxx&amp;gt;
> > &gt; &amp;gt; To: "A Ghoshal" &amp;lt;a.ghoshal@xxxxxxx&amp;gt;
> > &gt; &amp;gt; Cc: gluster-users@xxxxxxxxxxx,
> > &gt; &amp;gt; Sent: Wednesday, April 29, 2015 9:07:07 AM
> > &gt; &amp;gt; Subject: Re: client is terrible with large
> > amount of small files
> > &gt; &amp;gt;
> > &gt; &amp;gt; Hi Ghoshal,
> > &gt; &amp;gt;
> > &gt; &amp;gt; Please find the details below.
> > &gt; &amp;gt;
> > &gt; &amp;gt; A) Glusterfs version
> > &gt; &amp;gt; glusterfs 3.6.2
> > &gt;
> > &gt; Upgrade to 3.6.3 and set client.event-threads and server.event-threads
> > to at least 4. Here is a guide on tuning MT epoll:
> > &gt;
> > &gt;
> > &gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; B) volume configuration (gluster v &amp;lt;volname&amp;gt;
> > info)
> > &gt; &amp;gt; gluster volume info
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; Volume Name: integvol
> > &gt; &amp;gt; Type: Replicate
> > &gt; &amp;gt; Volume ID: b8f3a19e-59bc-41dc-a55a-6423ec834492
> > &gt; &amp;gt; Status: Started
> > &gt; &amp;gt; Number of Bricks: 1 x 3 = 3
> > &gt; &amp;gt; Transport-type: tcp
> > &gt; &amp;gt; Bricks:
> > &gt; &amp;gt; Brick1: integ-gluster2:/srv/sdb1/brick
> > &gt; &amp;gt; Brick2: integ-gluster1:/srv/sdb1/brick
> > &gt; &amp;gt; Brick3: integ-gluster3:/srv/sdb1/brick
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; C) host linux version
> > &gt; &amp;gt; CentOS release 6.5 (Final)
> > &gt;
> > &gt; Are your bricks on LVM? Are you using thinp? If so update to the
> > latest kernel as thinp perf was really bad in 6.5 and early 6.6 kernels.
> > &gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; D) details about the kind of network you use to connect your
> > servers making
> > &gt; &amp;gt; up your storage pool.
> > &gt; &amp;gt; We are connecting LAN to LAN there is no special network
> > configuration done
> > &gt; &amp;gt;
> > &gt; &amp;gt; Frome client we use to mount like below
> > &gt; &amp;gt; mount -t glusterfs gluster1:/integvol /mnt/gluster/
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; Regards
> > &gt; &amp;gt; Prabu
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; ---- On Wed, 29 Apr 2015 17:58:16 +0530 A
> > Ghoshal&amp;lt;a.ghoshal@xxxxxxx&amp;gt; wrote
> > &gt; &amp;gt; ----
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; Performance would largely depend upon setup. While I cannot
> > think of any
> > &gt; &amp;gt; setup that would cause write to be this slow, if would help
> > if you share the
> > &gt; &amp;gt; following details:
> > &gt; &amp;gt;
> > &gt; &amp;gt; A) Glusterfs version
> > &gt; &amp;gt; B) volume configuration (gluster v &amp;lt;volname&amp;gt;
> > info)
> > &gt; &amp;gt; C) host linux version
> > &gt; &amp;gt; D) details about the kind of network you use to connect your
> > servers making
> > &gt; &amp;gt; up your storage pool.
> > &gt; &amp;gt;
> > &gt; &amp;gt; Thanks,
> > &gt; &amp;gt; Anirban
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; From: gjprabu &amp;lt; gjprabu@xxxxxxxxxxxx &amp;gt;
> > &gt; &amp;gt; To: &amp;lt; gluster-users@xxxxxxxxxxx &amp;gt;
> > &gt; &amp;gt; Date: 04/29/2015 05:52 PM
> > &gt; &amp;gt; Subject: Re: client is terrible with large
> > amount of small
> > &gt; &amp;gt; files
> > &gt; &amp;gt; Sent by: gluster-users-bounces@xxxxxxxxxxx
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; Hi Team,
> > &gt; &amp;gt;
> > &gt; &amp;gt; If anybody know the solution please share us.
> > &gt; &amp;gt;
> > &gt; &amp;gt; Regards
> > &gt; &amp;gt; Prabu
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; ---- On Tue, 28 Apr 2015 19:32:40 +0530 gjprabu &amp;lt;
> > gjprabu@xxxxxxxxxxxx &amp;gt;
> > &gt; &amp;gt; wrote ----
> > &gt; &amp;gt; Hi Team,
> > &gt; &amp;gt;
> > &gt; &amp;gt; We are using glusterfs newly and testing data transfer part
> > in client using
> > &gt; &amp;gt; fuse.glusterfs file system but it is terrible with large
> > amount of small
> > &gt; &amp;gt; files (Large amount of small file 150MB of size it's writing
> > around 18min).
> > &gt; &amp;gt; I can able copy small files and syncing between the server
> > brick are working
> > &gt; &amp;gt; fine but it is terrible with large amount of small files.
> > &gt; &amp;gt;
> > &gt; &amp;gt; if anybody please share the solution for the above issue.
> > &gt; &amp;gt;
> > &gt; &amp;gt; Regards
> > &gt; &amp;gt; Prabu
> > &gt; &amp;gt;
> > &gt; &amp;gt; _______________________________________________
> > &gt; &amp;gt; Gluster-users mailing list
> > &gt; &amp;gt; Gluster-users@xxxxxxxxxxx
> > &gt; &amp;gt;
> > &gt; &amp;gt; _______________________________________________
> > &gt; &amp;gt; Gluster-users mailing list
> > &gt; &amp;gt; Gluster-users@xxxxxxxxxxx
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; =====-----=====-----=====
> > &gt; &amp;gt; Notice: The information contained in this e-mail
> > &gt; &amp;gt; message and/or attachments to it may contain
> > &gt; &amp;gt; confidential or privileged information. If you are
> > &gt; &amp;gt; not the intended recipient, any dissemination, use,
> > &gt; &amp;gt; review, distribution, printing or copying of the
> > &gt; &amp;gt; information contained in this e-mail message
> > &gt; &amp;gt; and/or attachments to it are strictly prohibited. If
> > &gt; &amp;gt; you have received this communication in error,
> > &gt; &amp;gt; please notify us by reply e-mail or telephone and
> > &gt; &amp;gt; immediately and permanently delete the message
> > &gt; &amp;gt; and any attachments. Thank you
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt;
> > &gt; &amp;gt; _______________________________________________
> > &gt; &amp;gt; Gluster-users mailing list
> > &gt; &amp;gt; Gluster-users@xxxxxxxxxxx
> > &gt;
> > &gt;
> > &gt;
> > &gt;
> > &gt;
> > &gt;
> > &gt;
> > &gt;
> > &gt; _______________________________________________
> > &gt; Gluster-users mailing list
> > &gt;
> >
> >
>
> --
> ~Atin
>





_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux