We tried, but the process which hits 100% CPU is glusterfsd, therefore, the impact on Gluster is still there, because that process is virtually at 100% CPU. -----Original Message----- From: James [mailto:purpleidea@xxxxxxxxx] Sent: 22 septembre 2014 13:25 To: Jocelyn Hotte Cc: justglusterfs@xxxxxxxxx; gluster-users@xxxxxxxxxxx; gluster-devel@xxxxxxxxxxx Subject: Re: glusterfs replica volume self heal lots of small file very very slow?how to improve? why slow? On Mon, Sep 22, 2014 at 10:04 AM, Jocelyn Hotte <jocelyn.hotte@xxxxxxxxxxx> wrote: > When a self-heal hits in our use-case, it is a direct impact in performance for the users. The CPU of the Gluster nodes hits 100%, and maintains this for usually 1 hour, but sometimes goes up to 4-5 hours. > This usually renders the Gluster cluster unusable, with a high impact for us. Have you tried using cgroups to limit the effect of self-heal? _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
