Earlier quoted context omitted.
Launchpad is such a shitty website, aimed at Ubuntu and only Ubuntu, links to source code or more information are nowhere to be found... Searching on Github, this seems to be it. Turns out, there's releases for Arch, Debian, etc. and it's even in the repositories. No need to add a ppa. https://github.com/graysky2/profile-sync-daemon For Debian and co: $ apt-cache show profile-sync-daemon $ sudo apt-get install profil…
I checked the Activity Monitor on OS X to see if it's the same and if I should do something. It's quite surprising: bird 11,38 GB 119,8 MB kernel_task 8,82 GB 23,0 MB launchd 8,46 GB 77,7 MB revisiond 8,35 GB 105,8 MB Tweetbot 3,01 GB 50,2 MB Safari 879,6 MB 10,0 MB mds_stores 726,2 MB 570,1 MB systemstatsd 695,0 MB 775,0 MB nsurlstorag 685,3 MB 9,5 MB Google Chrom 681,4 MB 303,5 MB iTerm2 653,7 MB 1,6 GB cfprefsd 50…
Heavy SSD Writes from Firefox
321–330 of 361 posts
Re: Heavy SSD Writes from Firefox
#322Re: Heavy SSD Writes from Firefox
#323Earlier quoted context omitted.
The warranty on your EVO is just 150 TBW. Yes, but endurance tests almost invariably show that the warranty ratings are extremely conservative. The 1TB 850 PRO (which uses exactly the same NAND chips as the 850 EVO, just a different controller) has been endurance tested to more than 7 Petabytes. See: http://packet.company/blog/ The older generations typically had better endurance, the newer generations are more dense…
No, you're wrong. The 850 PRO uses MLC while the EVO uses TLC. But given that they're both constructed on Samsung's 3D-VNAND technology, their endurance is still much higher than the competitors out there.
It's not "much" higher, actually, 3D MLC as implemented by Samsung is just "up to twice" better than the planar MLC given the same die area and capacity:
http://www.samsung.com/semiconductor/minisite/ssd/v-nand/tec...
"Samsung V-NAND provides up to twice the endurance of planar NAND."
But if the size of the cell drops, the number of P/E cycles drops. Samsung's endurance declarations are real and to be believed, they initially used bigger cells than some of their other chips (or competitors), but Samsung engineers know what they do, that "some tests" achieved "much more" can be either an accident or due to the errors in the test methodology (and I very much suspect the later, because it also allows the accidents to be taken as the "success"). At the time these SSDs appeared, Samsung declared twice less TBW than they do now, so now the declared endurance is surely not too pessimistic, but based on the real knowledge of what's inside.
Re: Heavy SSD Writes from Firefox
#324Hi, I’m one of the Firefox developers who was in charge of Session Restore, so I’m one of the culprits of this heavy SSD I/O. To make a long story short: we are aware of the problem, but fixing it for real requires completely re-architecturing Session Restore. That’s something we haven’t done yet, as Session Restore is rather safety-critical for many users, so this would need to be done very carefully, and with plent…
Re: Heavy SSD Writes from Firefox
#325Earlier quoted context omitted.
15 minutes of coding, perhaps. Then an hour of writing good tests. Then lots of manual and automated testing on four or five platforms, and fixing the weird issues you get on Windows XP SP2, or only on 64-bit Linux running in a VM, or whatever. Then making sure you don't regress startup performance (which you probably will unless you have a really, really slow disk). Then implementing rock solid migration so you can…
> regress startup performance No, for example, LZ4 is unbelievably fast: https://github.com/Cyan4973/lz4 almost 2 GB per second in decompression! I've just tried compressing some backupXX.session file (the biggest I've managed to find, just around 2 MB) and it compressed to 70% of the original, probably not enough to implement the compression -- and I suspect the reason is that the file contains too much base64 encod…
Re: Heavy SSD Writes from Firefox
#326Earlier quoted context omitted.
The warranty on your EVO is just 150 TBW. Yes, but endurance tests almost invariably show that the warranty ratings are extremely conservative. The 1TB 850 PRO (which uses exactly the same NAND chips as the 850 EVO, just a different controller) has been endurance tested to more than 7 Petabytes. See: http://packet.company/blog/ The older generations typically had better endurance, the newer generations are more dense…
No, you're wrong. The 850 PRO uses MLC while the EVO uses TLC. But given that they're both constructed on Samsung's 3D-VNAND technology, their endurance is still much higher than the competitors out there.
In all likelihood the drive will never get anywhere near any of these values - it'll be replaced with newer, better tech at some point. It may then get used for a backups or secondary storage, but in those scenarios the daily writes will drop enormously.
Re: Heavy SSD Writes from Firefox
#327Earlier quoted context omitted.
Some people are unjustifiably worried about SSD endurance. The reality is that even with fairly heavy use, most of them will far outlive the computers they're in. And their owners for that matter! I purchased my current SSD in March 2015 - it's a Samsung 850 EVO 512GB. It's done 7332 Power_On_Hours, and 36486573259 Total_LBAs_Written, which works out as just under 17 TB written, or about 31.6 GB/day. That kind of sou…
this is an incorrect assumption http://techreport.com/review/27909/the-ssd-endurance-experim... Most of the SSD failed before a petabyte... and started encountering lots of errors before that (forget about the Samsung Pro series which is the only one that survived till its multi-petabyte end).
If a 250GB 840 EVO can get to 800TB without errors, then I'd expect a 500GB 850 EVO to reach 1 PB, easily.
A 500GB 850 EVO has newer-generation, more durable NAND endurance and twice the capacity to work with.
Re: Heavy SSD Writes from Firefox
#328Earlier quoted context omitted.
Storing a lot of static images as JSON base64 encoded, every 15 seconds is certainly not something that users should be blamed ("some users have 300MB JSON files"), just the poor programming. It would be interesting if somebody would actually analyze what takes the most of the mentioned 300 MB. I see a lot of base64 encoded stuff, if they are "favicons," come-on. There are so many caches in Firefox already, JSON file…
Nobody is blaming the user for the 300Mb. It's just a factor we need to take in consideration. But yeah, storing favicon in Session Restore would be pretty bad. I didn't remember that it was the case, though.
https://news.ycombinator.com/item?id=12569999
700 KB of binary images in a 1.7 MB session file, which can be compressed only to the 70% of its size.
I also see a lot of things like \\u0440 which spends eight characters for one unicode character (in another file, not from me). But that file was reduced to 37% of initial size with LZ4. It seems LZ4 is still worth doing, if the content remains easily accessible with the external tools, e.g. lz4cli.
Re: Heavy SSD Writes from Firefox
#329Earlier quoted context omitted.
Or ramdisk if you have a stable system.
That would lose the point of a recovery system. I'd rather just turn it off.
So I think the session restore is almost always used in a case where firefox crashed, but the system is fine.
Re: Heavy SSD Writes from Firefox
#330Earlier quoted context omitted.
Storing a lot of static images as JSON base64 encoded, every 15 seconds is certainly not something that users should be blamed ("some users have 300MB JSON files"), just the poor programming. It would be interesting if somebody would actually analyze what takes the most of the mentioned 300 MB. I see a lot of base64 encoded stuff, if they are "favicons," come-on. There are so many caches in Firefox already, JSON file…
Nobody is blaming the user for the 300Mb. It's just a factor we need to take in consideration. But yeah, storing favicon in Session Restore would be pretty bad. I didn't remember that it was the case, though.