- Original Message -
> From: "Ric Wheeler"
> To: "Raghavendra Gowdappa" , "Saravanakumar Arumugam"
>
> Cc: "Gluster Devel" , "Ben Turner"
> , "Ben England"
>
These are gbench failures rather than smoke failures. If you know how to
debug dbench failures, please add comments on the bug and I'll get you the
logs you need.
On Tue, Sep 27, 2016 at 9:40 AM, Ravishankar N
wrote:
> On 09/27/2016 09:36 AM, Pranith Kumar Karampuri
On 09/27/2016 07:56 AM, Raghavendra Gowdappa wrote:
+Manoj, +Ben turner, +Ben England.
@Perf-team,
Do you think the gains are significant enough, so that smb and nfs-ganesha team
can start thinking about consuming this change?
regards,
Raghavendra
This is a large gain but I think that we
+Manoj, +Ben turner, +Ben England.
@Perf-team,
Do you think the gains are significant enough, so that smb and nfs-ganesha team
can start thinking about consuming this change?
regards,
Raghavendra
- Original Message -
> From: "Saravanakumar Arumugam"
> To:
On 09/27/2016 09:36 AM, Pranith Kumar Karampuri wrote:
hi Nigel,
Is there already a bug to capture these in the runs when
failures happen? I am not able to understand why this failure
happened: https://build.gluster.org/job/smoke/30843/console,
logs/cores would have helped. Let me know
hi Nigel,
Is there already a bug to capture these in the runs when failures
happen? I am not able to understand why this failure happened:
https://build.gluster.org/job/smoke/30843/console, logs/cores would have
helped. Let me know if I should raise a bug for this.
--
Pranith
hi,
I found the following two issues and fixed them:
Problems:
1) flush-behind is on by default, so just because write completes
doesn't mean
it will be on the disk, it could still be in write-behind's cache.
This
leads to failure where if you write from one mount and
> On Sep 23, 2016, at 8:59 PM, Jeff Darcy wrote:
>
>>> write-behind: implement causal ordering and other cleanup
>>
>>> Rules of causal ordering implemented:¬
>>
>>> - If request A arrives after the acknowledgement (to the app,¬
>>
>>> i.e, STACK_UNWIND) of another request
Hi,
I have carried out "basic" performance measurement with zero copy write
APIs.
Throughput of zero copy write is 57 MB/sec vs default write 43 MB/sec.*
*( I have modified Ben England's gfapi_perf_test.c for this. Attached
the same for reference )
We would like to hear how samba/
> Michael and I are happy to announce that the migration is now complete.
Thank you both for all of your hard work. :)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
On Mon, Sep 26, 2016 at 4:49 PM, Niels de Vos wrote:
> On Fri, Sep 23, 2016 at 08:44:14PM +0530, Pranith Kumar Karampuri wrote:
> > On Fri, Sep 23, 2016 at 6:12 PM, Jeff Darcy wrote:
> >
> > > > Jiffin found an interesting problem in posix xlator where we
> compatible to linux page cache will always to be a better practice
> way, because there is a lot local applications that has already rely
> on its semantics.
I don't think users even *know* how the page cache behaves. I don't
think even its developers do, in the sense of being able to define
On Fri, Sep 23, 2016 at 08:44:14PM +0530, Pranith Kumar Karampuri wrote:
> On Fri, Sep 23, 2016 at 6:12 PM, Jeff Darcy wrote:
>
> > > Jiffin found an interesting problem in posix xlator where we have never
> > been
> > > using setfsuid/gid (
On Mon, Sep 26, 2016 at 1:05 PM, Ryan Ding wrote:
>
> > On Sep 23, 2016, at 8:59 PM, Jeff Darcy wrote:
> >
> >>> write-behind: implement causal ordering and other cleanup
> >>
> >>> Rules of causal ordering implemented:¬
> >>
> >>> - If request A
Hi all,
GlusterFS-3.7.16 is on target to be released on Sep 30, 4 days from now.
In preparation for the release, maintainers please stop merging
anymore changes into release-3.7.
If any developer has a change that needs to be merged, please reply to
this email before end of day Sep 28.
At this
15 matches
Mail list logo