| 1 |
On Wednesday 13 October 2004 7:31 am, Robin H. Johnson wrote: |
| 2 |
> portage loop file is usually on disk, when a sync is needed: |
| 3 |
> 1. umount loop file |
| 4 |
> 2. copy loop file to /dev/shm or other fast place |
| 5 |
> 3. mount loop file again (from new location) |
| 6 |
> 4. run updates to loop filesystem ('cvs up; emerge metadata' or 'emerge |
| 7 |
> sync') 5. umount loop file, copy back to disk |
| 8 |
> 6. mount loop file again |
| 9 |
|
| 10 |
Since (from what I've heard) Portage's speed issues are mostly I/O, why not |
| 11 |
keep the mounted copy on a tmpfs and simply make an on-disk backup after |
| 12 |
syncing (and copy it back on rebooting)? |
| 13 |
|
| 14 |
On Thursday 14 October 2004 2:07 pm, Ned Ludd wrote: |
| 15 |
> New loopback size is 11M after reading this thread and dumping ChangeLog |
| 16 |
> & metadata.xml files which does seem like a perfectly feasible thing for |
| 17 |
> us to do. Removing leading/trailing whitespace and erroneous newlines |
| 18 |
> yielded no noticeable gains. |
| 19 |
|
| 20 |
11 MB of RAM may or may not seem reasonable to users depending on how often |
| 21 |
they do things with Portage. |
| 22 |
-- |
| 23 |
Luke-Jr |
| 24 |
Developer, Utopios |
| 25 |
http://utopios.org/ |
Archives