I'm very curious whether these improvements hold up over the next few days.
Please report back.
Sincerely,
Artem
--
Founder, Android Police <http://www.androidpolice.com>, APK Mirror
<http://www.apkmirror.com/>, Illogical Robot LLC
beerpla.net | @ArtemR <http://twitter.com/ArtemR>
On Wed, Aug 5, 2020 at 9:44 AM Computerisms Corporation <bob at
computerisms.ca>
wrote:
> Hi List,
>
> > So, we just moved into a quieter time of the day, but maybe I just
> > stumbled onto something. I was trying to figure out if/how I could
> > throw more RAM at the problem. gluster docs says write behind is not
a
> > cache unless flush-behind is on. So seems that is a way to throw ram
to
> > it? I put performance.write-behind-window-size: 512MB and
> > performance.flush-behind: on and the whole system calmed down pretty
> > much immediately. could be just timing, though, will have to see
> > tomorrow during business hours whether the system stays at a
reasonable
> > load.
>
> so reporting back that this seems to have definitely had a significant
> positive effect.
>
> So far today I have not seen the load average climb over 13 with the
> 15minute average hovering around 7. cpus are still spiking from time to
> time, but they are not staying maxed out all the time, and frequently I
> am seeing brief periods of up to 80% idle. glusterfs process still
> spiking up to 180% or so, but consistently running around 70%, and the
> brick processes still spiking up to 70-80%, but consistently running
> around 20%. Disk has only been above 50% in atop once so far today when
> it spiked up to 92%, and still lots of RAM left over. So far nload even
> seems indicates I could get away with a 100Mbit network connection.
> Websites are snappy relative to what they were, still a bit sluggish on
> the first page of any given site, but tolerable or close to. Apache
> processes are opening and closing right away, instead of stacking up.
>
> Overall, system is performing pretty much like I would expect it to
> without gluster. I haven't played with any of the other settings yet,
> just going to leave it like this for a day.
>
> I have to admit I am a little bit suspicious. I have been arguing with
> Gluster for a very long time, and I have never known it to play this
> nice. kind feels like when your girl tells you she is "fine";
> conversation has stopped, but you aren't really sure if it's
done...
>
> >
> > I will still test the other options you suggested tonight, though,
this
> > is probably too good to be true.
> >
> > Can't thank you enough for your input, Strahil, your help is truly
> > appreciated!
> >
> >
> >
> >
> >
> >
> >>
> >>>>
> >>>>
> >>>> Best Regards,
> >>>> Strahil Nikolov
> >>>>
> >>> ________
> >>>
> >>>
> >>>
> >>> Community Meeting Calendar:
> >>>
> >>> Schedule -
> >>> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> >>> Bridge: https://bluejeans.com/441850968
> >>>
> >>> Gluster-users mailing list
> >>> Gluster-users at gluster.org
> >>> https://lists.gluster.org/mailman/listinfo/gluster-users
> > ________
> >
> >
> >
> > Community Meeting Calendar:
> >
> > Schedule -
> > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> > Bridge: https://bluejeans.com/441850968
> >
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > https://lists.gluster.org/mailman/listinfo/gluster-users
> ________
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://bluejeans.com/441850968
>
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20200805/1346beb6/attachment.html>