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