On Wed, Jan 18, 2017 at 2:43 PM, Graham Leggett wrote:
> On 18 Jan 2017, at 3:38 PM, Jim Jagielski wrote:
>
>> That's a good overview... Yeah, it might be getter better, but it does
>> seem that the nature of the bugs implies it's also getting more
>> fragile.
On 18 Jan 2017, at 3:38 PM, Jim Jagielski wrote:
> That's a good overview... Yeah, it might be getter better, but it does
> seem that the nature of the bugs implies it's also getting more
> fragile. Could be, likely is, just my impression due to some weird
> things I've seen
> On Jan 18, 2017, at 8:25 AM, Luca Toscano wrote:
>
>
>
> 2017-01-18 14:00 GMT+01:00 Jim Jagielski :
>
> > On Jan 18, 2017, at 7:50 AM, Graham Leggett wrote:
> >
> > On 17 Jan 2017, at 7:40 PM, Luca Toscano
2017-01-18 13:50 GMT+01:00 Graham Leggett :
> On 17 Jan 2017, at 7:40 PM, Luca Toscano wrote:
>
> > Since this email thread seems important, is there any update from
> anybody working on it? It would be great to open a bugzilla task otherwise,
> to track
2017-01-18 14:00 GMT+01:00 Jim Jagielski :
>
> > On Jan 18, 2017, at 7:50 AM, Graham Leggett wrote:
> >
> > On 17 Jan 2017, at 7:40 PM, Luca Toscano wrote:
> >
> >> Since this email thread seems important, is there any update from
>
> On Jan 18, 2017, at 8:14 AM, Graham Leggett wrote:
>
> On 18 Jan 2017, at 3:05 PM, Jim Jagielski wrote:
>
>> Well, there's this, and it seems like there are issues w/
>> the current mutexing as well, causing weird wake-ups.
>
> Only solution really is to
On 18 Jan 2017, at 3:05 PM, Jim Jagielski wrote:
> Well, there's this, and it seems like there are issues w/
> the current mutexing as well, causing weird wake-ups.
Only solution really is to find the bugs and fix them.
Regards,
Graham
—
smime.p7s
Description: S/MIME
> On Jan 18, 2017, at 8:01 AM, Graham Leggett wrote:
>
> On 18 Jan 2017, at 3:00 PM, Jim Jagielski wrote:
>
>> Somewhat on-topic but also off-topic as well, but it does seem
>> that event on trunk is getting much more fragile instead of more
>> stable. It
On 18 Jan 2017, at 3:00 PM, Jim Jagielski wrote:
> Somewhat on-topic but also off-topic as well, but it does seem
> that event on trunk is getting much more fragile instead of more
> stable. It seems to be picking up some kruft which is making
> event on trunk a *worse* option
> On Jan 18, 2017, at 7:50 AM, Graham Leggett wrote:
>
> On 17 Jan 2017, at 7:40 PM, Luca Toscano wrote:
>
>> Since this email thread seems important, is there any update from anybody
>> working on it? It would be great to open a bugzilla task
On 17 Jan 2017, at 7:40 PM, Luca Toscano wrote:
> Since this email thread seems important, is there any update from anybody
> working on it? It would be great to open a bugzilla task otherwise, to track
> everything and make sure that we don't forget about it :)
I
2016-09-18 10:57 GMT+02:00 Stefan Fritsch :
> Hi Graham,
>
> On Wed, 14 Sep 2016, Graham Leggett wrote:
>
> > On 06 Sep 2016, at 12:06 AM, Stefan Fritsch wrote:
> >
> > > in trunk, when having a lot of slow long running transfers, most of
> them seem
> > > to
Hi Graham,
On Wed, 14 Sep 2016, Graham Leggett wrote:
> On 06 Sep 2016, at 12:06 AM, Stefan Fritsch wrote:
>
> > in trunk, when having a lot of slow long running transfers, most of them
> > seem
> > to hog a thread and only a few of them go into async write completion mode.
On 06 Sep 2016, at 12:06 AM, Stefan Fritsch wrote:
> in trunk, when having a lot of slow long running transfers, most of them seem
> to hog a thread and only a few of them go into async write completion mode.
> Compare this to 2.4, where many transfers are doing async write
On Mon, Sep 5, 2016 at 6:06 PM, Stefan Fritsch wrote:
> Hi,
>
> in trunk, when having a lot of slow long running transfers, most of them seem
> to hog a thread and only a few of them go into async write completion mode.
> Compare this to 2.4, where many transfers are doing async
15 matches
Mail list logo