zlacker

[parent] [thread] 14 comments
1. london+(OP)[view] [source] 2023-07-18 12:30:49
Try clearing your profile.

Turns out having years of history, extensions, and a multi-gigabyte cache makes any browser slow.

replies(2): >>Avaman+C >>p-e-w+K
2. Avaman+C[view] [source] 2023-07-18 12:34:39
>>london+(OP)
Chrome automatically prunes history for quite a while now. Which I personally dislike, as I sometimes need to find something I visited a long time ago.
replies(1): >>justin+25
3. p-e-w+K[view] [source] 2023-07-18 12:35:11
>>london+(OP)
That's like saying "If your car runs too slow, toss out the back seats."

History and extensions are there for a reason. And managing the cache is the browser's job, not the user's.

replies(3): >>askl+X1 >>throwa+bh >>yborg+Vz
◧◩
4. askl+X1[view] [source] [discussion] 2023-07-18 12:43:00
>>p-e-w+K
You can also save some more weight by never filling the gas tank up to more than 25% capacity.
replies(1): >>dylan6+B7
◧◩
5. justin+25[view] [source] [discussion] 2023-07-18 13:01:03
>>Avaman+C
Firefox does the same thing too unfortunately, and it doesn't seem like it can be turned off.

It's a real pita for the same reason. Needed to look at browser history older than a few months and discovering it's all been deleted (by Firefox) was a very unpleasant experience.

Seems to be a needless data loss "optimisation" (sic), but I have no idea what the real world use case for that would be.

replies(2): >>wackge+D5 >>osmark+uc
◧◩◪
6. wackge+D5[view] [source] [discussion] 2023-07-18 13:04:32
>>justin+25
Not sure if I've done anything special but I've got history going back to 2021.
replies(1): >>justin+36
◧◩◪◨
7. justin+36[view] [source] [discussion] 2023-07-18 13:07:00
>>wackge+D5
Interesting. That gives me hope that there might indeed be a setting to change the behaviour. Thanks. :)
replies(2): >>alpaca+Rf >>svl+ed1
◧◩◪
8. dylan6+B7[view] [source] [discussion] 2023-07-18 13:15:04
>>askl+X1
But that makes high speed chases impractical as you have to keep stopping for gas
replies(1): >>fullst+hq
◧◩◪
9. osmark+uc[view] [source] [discussion] 2023-07-18 13:35:38
>>justin+25
I wrote a script (https://github.com/osmarks/random-stuff/blob/master/histrete...) to dump a Firefox places.sqlite database to a separate SQLite database for long-term storage (I run it nightly). It seems to delete stuff based on some combination of visit frequency and last visit time.

I suspect they need to do this to keep history searches fast, since I also separately hacked a bunch of `about:config` options to retain more history and they run quite slowly now, particularly on my phone.

◧◩◪◨⬒
10. alpaca+Rf[view] [source] [discussion] 2023-07-18 13:47:46
>>justin+36
There's a good chance an about:config setting lets you change it. FF has a ton of detailed settings but most are hidden.

On my setup the "manage history" window goes back a bit over 6 months. Unfortunately the list entries don't show a date, so I can't give more precise numbers.

◧◩
11. throwa+bh[view] [source] [discussion] 2023-07-18 13:51:50
>>p-e-w+K
You still have to regularly give your (ICE) car an oil change in order to keep it in proper working order.
◧◩◪◨
12. fullst+hq[view] [source] [discussion] 2023-07-18 14:22:23
>>dylan6+B7
You reminded me of this sketch: https://www.youtube.com/watch?v=cxY0-Qr_l78
◧◩
13. yborg+Vz[view] [source] [discussion] 2023-07-18 14:54:05
>>p-e-w+K
It's more like saying stop carrying around the cassette boombox and corpses of your last 3 dogs in the back seats.
◧◩◪◨⬒
14. svl+ed1[view] [source] [discussion] 2023-07-18 17:07:45
>>justin+36
browser.history.maxStateObjectSize and places.history.expiration.max_pages (both accessible through about:config) should be the settings to modify. Do a web search for those properties to get more information on how they interact.
replies(1): >>justin+DI2
◧◩◪◨⬒⬓
15. justin+DI2[view] [source] [discussion] 2023-07-19 02:58:42
>>svl+ed1
Fantastic! Thank you. :)
[go to top]