| 1 |
> > I believe gentoo-stats is already sampling a lot of the needed |
| 2 |
> > information. An estimate could primarly be based on some "major" |
| 3 |
> > factors; perhaps cpu-type and clock frequency. Then, if enough |
| 4 |
> > statistics is available for the current architecture, on other settings |
| 5 |
> > as well, sucb as -O flags and size of main memory (MAKEOPTS?). A kind of |
| 6 |
> > hierarchical estimate... Could perhaps be hard to implement in practice |
| 7 |
> > though (?). |
| 8 |
> > |
| 9 |
> > But I believe there probably is some limited set of factors that could |
| 10 |
> > provide a reasonably good estimate. |
| 11 |
> |
| 12 |
> Whoever actually implements these ideas, please don't forget that you need |
| 13 |
> a solution for capturing accurate stats on machines that use Portage's |
| 14 |
> distcc support. Because otherwise, your stats will not be as accurate as |
| 15 |
> you'd like. |
| 16 |
|
| 17 |
Yeah, this crossed my mind also. I believe that using distcc would "void" |
| 18 |
those stats, perhaps we can store it and maybe possible analyze if we can use |
| 19 |
any of it. |
| 20 |
|
| 21 |
Rutger |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
gentoo-dev@g.o mailing list |
Archives