3 ms·
Unless you care about latency. Just because an indexer ran through my hard drive doesn't mean I should have to wait 60+ seconds next time I log in for everythin
by coryrc 12y ago
Unless you care about latency. Just because an indexer ran through my hard drive doesn't mean I should have to wait 60+ seconds next time I log in for everything to page back into memory.
- colanderman 12y agoI haven't had this experience in 10 years of using a desktop system that updates the locate DB every night.
- shiven 12y agoSince we are sharing Anecdata, my experience is quite the opposite of yours. SSDs might be the middle path here.
- Rapzid 12y agoNah, I cultivate Chrome tabs. After sleeping my computer for a month, playing games, running VM's, doing clojure programming, etc; I found switching to an old Chrome tab or maximizing that Clojure book I hadn't looked at in 3 weeks would cause quite the pause. This is with SSD's all the way down.
- suprjami 12y agoIf you think swap introduces latency, you need to learn a lot about memory management.
- dale-cooper 12y agoSo, if your working set (files, application memory, etc) fits in memory, how does swap not introduce latency?
- scott_s 12y agoSome pages of memory in your working set may be rarely used. If so, then allocating physical pages of memory may be a waste. The kernel may be able to get better performance by using those pages for the disk cache - decreasing latency by hitting the disk less.
- noise 12y agolocate indexer cronjob should never be enabled on a production box. Problem solved.