Roger that.
I've deployed a new version with the patch
from a290da25a16b7c79d4a7a87f522b4068bca04979 - I'll leave it for a few
days and report back.
Please let me know if you think there are any further issues, or any
subsequent extra patches on top that are relevant.
Thanks!
Cheers,
Just
On Mon, Sep 19, 2016 at 11:04:29AM +0100, Justin Cattle wrote:
> I *think* I have answered my own question. The patch in the email doesn't
> include the switch to xmalloc that was originally in
> the krt-export-filtr-fix branch as well.
>
> I can see from `git blame` that it's in the previous com
I *think* I have answered my own question. The patch in the email doesn't
include the switch to xmalloc that was originally in
the krt-export-filtr-fix branch as well.
I can see from `git blame` that it's in the previous commit,
bc00f058154bb4a630d24d64a55b5f181d235c63 [ Filter: Prefer xmalloc/x
Ok - great.
Should this patch apply to the 1.6 released version ok ?
I was tracking from the krt-export-filtr-fix before, that that is now gone
:)
Cheers,
Just
On 19 September 2016 at 10:13, Ondrej Zajicek
wrote:
> On Mon, Sep 19, 2016 at 09:46:03AM +0100, Justin Cattle wrote:
> > Hi Pavel,
On Mon, Sep 19, 2016 at 09:46:03AM +0100, Justin Cattle wrote:
> Hi Pavel,
>
>
> After running with this latest fixup commit for a week, I see mixed results.
>
> With the first fix you created, all the processes remained using a very
> small amount of memory, consistently. As per my previous em
Hi Pavel,
After running with this latest fixup commit for a week, I see mixed results.
With the first fix you created, all the processes remained using a very
small amount of memory, consistently. As per my previous email, around
80Mg.
With the second fix, some of the bird processes are using u
