You are not logged in.
It is an old laptop from around 2010? with an hdd, boot time is around 1:30 minutes...
Maybe there is some other cache as well. See you later after a reboot.
Edit: After a reboot, it is still 2-3s now.
Last edited by progandy (2018-06-01 17:53:13)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
It is an old laptop from around 2010? with an hdd, boot time is around 1:30 minutes...
That would definitely be something wrong.
But I don't see why you'd see a speedup when dropping the cache.
I *very* predictably get:
$ time pacman -Q bash > /dev/null
real 0m2.602s
user 0m0.028s
sys 0m0.037s
After dropping the cache
Either running pacman-optimize, *or* running pacman -Q bash a second time without dropping the cache, results in an identical speedup to:
$ time pacman -Q bash > /dev/null
real 0m0.056s
user 0m0.015s
sys 0m0.010s
This includes before having ever run pacman-optimize...
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
But I don't see why you'd see a speedup when dropping the cache.
I saw the speedup after running pacman-optimize and dropping the cache to remove the placebo effect. So I guess in my case it worked?
Cached access was always very fast. <0.2 seconds
[OT] Oh well, it is time for a new laptop anyways. At least there are a few reasonable options with amd graphics again.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Thanks progandy. So there's a sample size of one showing it worked.
But placebos do work too
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline