[Gluster-devel] Gluster Benchmark Kit
Ben Turner
bturner at redhat.com
Wed Apr 29 13:14:58 UTC 2015
----- Original Message -----
> From: "M S Vishwanath Bhat" <msvbhat at gmail.com>
> To: "Benjamin Turner" <bennyturns at gmail.com>
> Cc: "Kiran Patil" <kiran at fractalio.com>, gluster-users at gluster.org, "Gluster Devel" <gluster-devel at gluster.org>,
> bturner at redhat.com
> Sent: Wednesday, April 29, 2015 3:20:12 AM
> Subject: Re: [Gluster-devel] Gluster Benchmark Kit
>
> On 28 April 2015 at 01:03, Benjamin Turner <bennyturns at gmail.com> wrote:
>
> > Hi Kiran, thanks for the feedback! I already put up a repo on githib:
> >
> > https://github.com/bennyturns/gluster-bench
> >
> > On my TODO list is:
> >
> > -The benchmark is currently RHEL / RHGS(Red Hat Gluster Storage) specific,
> > I want to make things work with at least non paid RPM distros and Ubuntu.
> > -Other filesystems(like you mentioned)
> > -No LVM and non thinp config options.
> > -EC, tiering, snapshot capabilities.
> >
> > I'll probably fork things and have a Red Hat specific version and an
> > upstream version. As soon as I have everything working on Centos I'll let
> > the list know and we can enhance things to do whatever we need. I always
> > thought it would be interesting if we had a page where people could submit
> > their benchmark data and the HW / config used. Having a standard tool /
> > tool set will help there.
> >
>
> Ben,
>
> Do you think it is a good Idea (or is it possible) to integrate these with
> distaf? (https://github.com/gluster/distaf)
When I made this my goal was for someone to be able to build a cluster from scratch and run the full benchmark suite with only like 3-4 commands. I specifically didn't use distaf to cut down on complexity, because the test tools were all already multinode capable, and I am already maintaining the rhs-system-init script I figured I would just reuse that for the setup. That said I have been seeing more and more reasons to move things to distaf(FIO is not multi node capable, gather profiling data from each server, etc), and I was kicking around the idea of DISTAF-ifing it. Let me fix everything to work with Centos/Fedora and get it into git. From there we can look at distaf-ifing things, but I agree that is the way things should go.
-b
> That would enable us to choose workloads suitable to each scenario for
> single (set of) tests.
>
> Best Regards,
> Vishwanath
>
>
> >
> > -b
> >
> >
> > On Mon, Apr 27, 2015 at 3:31 AM, Kiran Patil <kiran at fractalio.com> wrote:
> >
> >> Hi,
> >>
> >> I came across "Gluster Benchmark Kit" while reading [Gluster-users]
> >> Disastrous performance with rsync to mounted Gluster volume thread.
> >>
> >> http://54.82.237.211/gluster-benchmark/gluster-bench-README
> >>
> >> http://54.82.237.211/gluster-benchmark
> >>
> >> The Kit includes tools such as iozone, smallfile and fio.
> >>
> >> This Kit is not documented and need to baseline this tool for Gluster
> >> Benchmark testing.
> >>
> >> The community is going to benefit by adopting and extending it as per
> >> their needs and the kit should be hosted on Github.
> >>
> >> The init.sh script in the Kit contains only XFS filesystem which can be
> >> extended to BTRFS and ZFS.
> >>
> >> Thanks Ben Turner for sharing it.
> >>
> >> Kiran.
> >>
> >> _______________________________________________
> >> Gluster-devel mailing list
> >> Gluster-devel at gluster.org
> >> http://www.gluster.org/mailman/listinfo/gluster-devel
> >>
> >>
> >
> > _______________________________________________
> > Gluster-devel mailing list
> > Gluster-devel at gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> >
> >
>
More information about the Gluster-devel
mailing list