Displaying 3 results from an estimated 3 matches for "13m10s".
2016 Mar 01
2
Add support for in-process profile merging in profile-runtime
...any different factors: write
> latency, the rate at which the instrumented binary retires, io
> throughput/network bandwidth etc).
>
> 1) SSD
>
> The performance is almost identical across *ALL* the test configurations.
> The real time needed to complete the full self build is ~13m10s. There is
> no visible file contention with file locking enabled even with pool size ==
> 1.
>
> 2) tmpfs
>
> only tested with the following configs
> a) shared profile with no merge
> b) with merge (pool == 1), with merge (pool == 2)
>
> Not surprisingly, the result...
2016 Feb 28
3
Add support for in-process profile merging in profile-runtime
On Sat, Feb 27, 2016 at 6:50 PM, Sean Silva <chisophugis at gmail.com> wrote:
> I have thought about this issue too, in the context of games. We may want
> to turn profiling only for certain frames (essentially, this is many small
> profile runs).
>
> However, I have not seen it demonstrated that this kind of refined data
> collection will actually improve PGO results in
2016 Feb 28
0
Add support for in-process profile merging in profile-runtime
I have thought about this issue too, in the context of games. We may want
to turn profiling only for certain frames (essentially, this is many small
profile runs).
However, I have not seen it demonstrated that this kind of refined data
collection will actually improve PGO results in practice.
The evidence I do have though is that IIRC Apple have found that almost all
of the benefits of PGO for