1 |
On Sunday 19 January 2014 11:59:36 Mike Gilbert wrote: |
2 |
> On Sun, Jan 19, 2014 at 4:44 AM, Mike Frysinger <vapier@g.o> wrote: |
3 |
> > Chromium OS for a long time was restricted to EAPI 4 for two reasons -- |
4 |
> > it had an old portage version (and upgrading to a newer one regressed |
5 |
> > performance significantly, so we held off until we could figure out why) |
6 |
> |
7 |
> I am curious to know more about the performance regression if you can |
8 |
> share. Is that something that got fixed, or did you disable some |
9 |
> features (like the slot-operator stuff)? |
10 |
|
11 |
we finally tracked it down (was due to new the new FEATURES=merge-sync option. |
12 |
when you're installing 200 to 500 binary packages (with like 32 in parallel), |
13 |
that can easily choke your throughput. some systems saw really excessive |
14 |
latencies (which i would guess was due to their drive taking longer to process |
15 |
dirty blocks). but it took us some time to figure that out as we were making a |
16 |
large version jump and we didn't have too much time to dedicate to tracking it |
17 |
down. lots o bugs to fix. |
18 |
-mike |