You are not logged in.
Hey guys,
I recently picked up a SSD and have become extreamly paranoid of applications doing too much writing too it.
Looking at iotop while chrome's running I see a lot of disk writes coming from libpepflashplayer.so
05:39:13 6814 be/4 evan 0.00 K/s 29.59 K/s 0.00 % 1.06 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [BrowserBlocking]
05:39:13 331 be/3 root 0.00 K/s 14.80 K/s 0.00 % 0.70 % [jbd2/sda4-8]
05:39:17 6799 be/4 evan 0.00 K/s 37.11 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:17 6811 be/4 evan 0.00 K/s 160.66 K/s 0.00 % 2.15 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [BrowserBlocking]
05:39:17 331 be/3 root 0.00 K/s 14.61 K/s 0.00 % 1.13 % [jbd2/sda4-8]
05:39:17 6799 be/4 evan 0.00 K/s 7.30 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:18 6794 be/4 evan 0.00 K/s 331.91 K/s 0.00 % 3.64 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_DBThread]
05:39:18 6799 be/4 evan 0.00 K/s 7.38 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:18 6799 be/4 evan 0.00 K/s 501.13 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:18 6827 be/4 evan 0.00 K/s 103.17 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_HistoryT]
05:39:19 6799 be/4 evan 0.00 K/s 1250.51 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:19 6799 be/4 evan 0.00 K/s 1377.86 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:20 6799 be/4 evan 0.00 K/s 2078.74 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:21 6799 be/4 evan 0.00 K/s 118.37 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:21 6799 be/4 evan 0.00 K/s 689.73 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:21 6814 be/4 evan 0.00 K/s 7.34 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [BrowserBlocking]
05:39:22 6796 be/4 evan 0.00 K/s 59.51 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_FileThre]
05:39:22 6799 be/4 evan 0.00 K/s 676.88 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:23 6799 be/4 evan 0.00 K/s 7.40 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:24 162 be/4 root 0.00 K/s 140.07 K/s 0.00 % 0.00 % systemd-journald
05:39:25 6796 be/4 evan 0.00 K/s 66.80 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_FileThre]
05:39:26 331 be/3 root 0.00 K/s 162.95 K/s 0.00 % 0.62 % [jbd2/sda4-8]
05:39:26 6844 be/4 evan 0.00 K/s 22.22 K/s 0.00 % 0.10 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [BrowserBlocking]
05:39:28 6835 be/4 evan 0.00 K/s 207.50 K/s 0.00 % 0.99 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_SyncThre]
05:39:28 331 be/3 root 0.00 K/s 14.81 K/s 0.00 % 1.87 % [jbd2/sda4-8]
05:39:28 6827 be/4 evan 0.00 K/s 118.50 K/s 0.00 % 0.85 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_HistoryT]
05:39:28 6796 be/4 evan 0.00 K/s 22.22 K/s 0.00 % 0.09 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_FileThre]
05:39:29 6794 be/4 evan 0.00 K/s 44.46 K/s 0.00 % 1.15 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_DBThread]
05:39:36 6799 be/4 evan 0.00 K/s 51.79 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:37 331 be/3 root 0.00 K/s 124.82 K/s 0.00 % 1.60 % [jbd2/sda4-8]
05:39:37 6835 be/4 evan 0.00 K/s 110.13 K/s 0.00 % 0.91 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_SyncThre]
05:39:37 6799 be/4 evan 0.00 K/s 308.37 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:38 6799 be/4 evan 0.00 K/s 405.67 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_CacheThr]
05:39:38 6811 be/4 evan 0.00 K/s 14.75 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [BrowserBlocking]
05:39:38 6827 be/4 evan 0.00 K/s 88.51 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_HistoryT]
05:39:38 6844 be/4 evan 0.00 K/s 7.42 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [BrowserBlocking]
05:39:39 6827 be/4 evan 0.00 K/s 14.59 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_HistoryT]
05:39:39 331 be/3 root 0.00 K/s 44.04 K/s 0.00 % 0.74 % [jbd2/sda4-8]
05:39:39 6814 be/4 evan 0.00 K/s 249.55 K/s 0.00 % 0.14 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [BrowserBlocking]
05:39:40 331 be/3 root 0.00 K/s 21.77 K/s 0.00 % 0.75 % [jbd2/sda4-8]
05:39:40 6796 be/4 evan 0.00 K/s 217.73 K/s 0.00 % 0.09 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_FileThre]
05:39:40 6811 be/4 evan 0.00 K/s 21.77 K/s 0.00 % 0.03 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [BrowserBlocking]
05:39:41 6796 be/4 evan 0.00 K/s 7.40 K/s 0.00 % 0.00 % libpepflashplayer.so --ppapi-flash-version=11.8.800.97 [Chrome_FileThre]Even with the plugin disabled in chrome://plugins I still see the same ammount of IO.
Any ideas why it's making so many writes?
Last edited by EvanPurkhiser (2013-07-19 09:51:38)
Offline
OK, after removing chrome-pepper-flash I now see entries in iotop that look like
05:45:42 8041 be/4 evan 0.00 K/s 14.75 K/s 0.00 % 0.00 % chromium [Chrome_FileThre]
05:45:49 8041 be/4 evan 0.00 K/s 7.40 K/s 0.00 % 0.00 % chromium [Chrome_FileThre]So I'm going to chalk this up to normal chromium disk activity.
Offline
just a quick follow-up.
chromium updates own /proc/*/cmdline with something in slightly different format, spaces instead of null bytes.
iotop cannot handle that very well:
"libpepflashplayer.so ..." is a red herring,
actual process is "/usr/lib/chromium/chromium --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.8.800.154"
Offline
I recently picked up a SSD and have become extreamly paranoid of applications doing too much writing too it.
As long as you bought a decent SSD, I wouldn't worry about this too much. In the early days, when the firmware was still you and it sucked, the wear levelling didn't work properly and disks would prematurely die. But these days, with new disks, it has been found that the controller will likely die long before the flash wears out.
I have a Samsung 840 250GiB, which as you may or may not know, is Triple Level Cell (TLC). If you also know anything about SSD flash, the originals were Single Level Cell and the SLC these days can sometimes do 100,000 write cycles. Multi-Level Cell (MLC) consumer disks are typically rated for 3000 to 5000 write cycles. So as you can guess, this means my TLC is significnatly lower than the MLC. But I have seen a couple tests with these 840s, where it was just constantly written to at a write amplification of 1 (you'll never actually see this low of a write amplification in real life), and it lasted for several months. At that level, it was determined that under "normal use" it would last something like ~160 years. Even with a rather high write amplification of 10, that would still be 16 years. So don't worry about it. Just use it.
In any case, I also don't like how much chromium writes to the disk, but this would be the case whether I was using an SDD or an HDD. So I use the /etc/chromium/default config to also add "--disk-cache-dir=/tmp". This is also where those pappi switches can be found (the post_install function of the pappi package writes this for you). That switch will make a directory /tmp/Cache, where chromium will store its cached web pages. This would otherwise be in ~/.cache/chromium/Cache I believe. Your normal profile, passwords, form info, bookmarks, etc. are all stored in ~/.config, so you don't be losing any of that.
Offline