| 1 |
On Thu, Sep 6, 2012 at 10:20 AM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
> Nicolas Sebrecht wrote: |
| 3 |
>> The 06/09/12, Dale wrote: |
| 4 |
>> |
| 5 |
>>> Not quite. The theory is that if you put portages work directory on |
| 6 |
>>> tmpfs, then all the writes and such are done in ram which is faster. |
| 7 |
>> No! This is too much simplistic view to explain what you see. |
| 8 |
>> |
| 9 |
>> In practice, _all_ the writes always happen in RAM whatever backend |
| 10 |
>> storage you use. |
| 11 |
>> |
| 12 |
>> The difference you could see is if there is not enough RAM for the |
| 13 |
>> kernel cache, it will have to wait for the backend storage. |
| 14 |
>> |
| 15 |
> |
| 16 |
> |
| 17 |
> OK. Step by step here so hopefully you and Neil can follow. |
| 18 |
> |
| 19 |
> Freshly booted system. |
| 20 |
> Clear caches just to be sure |
| 21 |
> |
| 22 |
> emerge foo with portages work directory on tmpfs |
| 23 |
> clear caches again |
| 24 |
> emerge foo with portages work directory on disk |
| 25 |
> clear caches again. |
| 26 |
> emerge foo with portages work directory on tmpfs |
| 27 |
> clear caches again |
| 28 |
> emerge foo with portages work directory on disk |
| 29 |
> |
| 30 |
> You repeat this enough times and you see that it doesn't matter if |
| 31 |
> portage's work directory is on disk or on tmpfs. |
| 32 |
|
| 33 |
If you have enough RAM, then this is certainly true. Nobody is |
| 34 |
disputing that. They've been trying to explain that there's a |
| 35 |
difference when you _don't_ have that much RAM, and they've been |
| 36 |
trying to explain the mechanism behind that. |
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
:wq |
Archives