Greg!
Thanks for the explanation and sorry for the report. I’m putting the attachment
to dropbox, to work around the mailing list size cap.
> On 25 Apr 2017, at 08:36, Greg Parker (mailto:gpar...@apple.com)> wrote:
>
> > On Apr 24, 2017, at 8:52 PM, Pavol Vaskovic > (mailto:p...@pali.sk)>
> On Apr 24, 2017, at 8:52 PM, Pavol Vaskovic wrote:
>
>> On 25 Apr 2017, at 01:28, Greg Parker wrote:
>>
>> The value of MAX_RSS depends on OS behavior. Other activity on the same
>> machine may change MAX_RSS of the benchmark.
>
> Can you please describe the mechanism of how “other activit
> On 25 Apr 2017, at 01:28, Greg Parker wrote:
>
> The value of MAX_RSS depends on OS behavior. Other activity on the same
> machine may change MAX_RSS of the benchmark.
Can you please describe the mechanism of how “other activity on the same
machine may change MAX_RSS of the benchmark”.?
>
> On Apr 21, 2017, at 3:57 AM, Pavol Vaskovic via swift-dev
> wrote:
>
> Hi swift-dev!
>
> I was working over the Easter holiday weekend on script that reports the
> benchmark results comparison. I wasn’t always up-to-date with the master, but
> I have noticed a mysterious change in MAX_R
On Fri, Apr 21, 2017 at 7:55 PM, Michael Gottesman
wrote:
>
> I can't think of anything. But what I can say is that this makes me want
> to track MAX_RSS over time ; ).
>
SR-4591 Performance monitoring: History of benchmark results
https://bugs.swift.org/browse/SR-4591
_
> On Apr 21, 2017, at 3:57 AM, Pavol Vaskovic via swift-dev
> wrote:
>
> Hi swift-dev!
>
> I was working over the Easter holiday weekend on script that reports the
> benchmark results comparison. I wasn’t always up-to-date with the master, but
> I have noticed a mysterious change in MAX_RS
Hi swift-dev!
I was working over the Easter holiday weekend on script that reports the
benchmark results comparison. I wasn’t always up-to-date with the master, but I
have noticed a mysterious change in MAX_RSS value reported from benchmarks. The
change went away again in later builds.
For e
