Neil Bothwick wrote: > On Thu, 06 Sep 2012 04:15:23 -0500, Dale wrote: > >>> You missed the point. One of the first thing emerge will do is to >>> uncompress the package. At this time, all the files are cached in RAM. >>> Hence, everything needed for the build/compilation will come from the >>> cache like it would do with tmpfs. >>> >> You miss this point not me. I *cleared* that cache. From kernel.org: > Sorry Dale, but you are missing the point. You cleared the cache before > running emerge, then ran emerge. The first thing emerge did was unpack > the tarball and populate the disk cache. All clearing the disk cache did > was make sure there was plenty of space to cache the new data, thus > speeding up the process. > >
Then explain to me why it was at times slower while on tmpfs? Trust me, I ran this test many times and in different orders and it did NOT make much if any difference. I might add, the cache on the drive I was using is nowhere near large enough to cache the tarball for the package. Heck, the cache on my current system drive is only 8Mbs according to hdparm. That is not much since I tested using much larger packages. You can't cache files larger than the cache. Do I need to run a test, reboot, run the test again to show this is not making much if any difference? I mean, really? o_O Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
