Rubyw.exe drive writes
Is it normal for rubyw.exe to be constantly writing information to
disk? At idle, every second rubyw.exe receives 64 bytes of data and
writes 20 kilobytes to disk. What information needs to be written so
often?
Listening to a mechanical drive being continuously
accessed by this program is grating on my nerves. It's just
never-ending drive writes; all day, every day.
Edit: I should note that after disconnecting from the VPN rubyw.exe still writes 3k+.
disk? At idle, every second rubyw.exe receives 64 bytes of data and
writes 20 kilobytes to disk. What information needs to be written so
often?
Listening to a mechanical drive being continuously
accessed by this program is grating on my nerves. It's just
never-ending drive writes; all day, every day.
Edit: I should note that after disconnecting from the VPN rubyw.exe still writes 3k+.
Comments
[05/04/14 17:35:59] connection_status: CONNECTED
[05/04/14 17:35:59] reset_bad_state
And it logs that EVERY second. Is the "reset_bad_state" normal?
Is there a way to prevent Ruby from logging this redundant information so often? Or turn off logging altogether? I can't imagine the PIA_manager needs to read a log file as any data it needs must surely be read from memory prior to it being written... right?
Utilizing Sysinternals Process Monitor, I see rubyw.exe accesses:
\pia_manager\nolog
\pia_manager\data\command_file.txt
\pia_manager\log\pia_manager.log
\pia_manager\log\openvpn.pid
All of the files appear in their respective directories except for "nolog". Apparently, Ruby tries to create this file, but returns a "name not found". Unable to create this file for some reason?
The most activity seems to involve "openvpn.pid"; Ruby creates the file, followed by many "buffer overflow" responses. From what I have read, this means that the memory alloted is not large enough for the data that the process is attempting to manage. I have no idea if this is usual or if it affects performance.
At any rate, I think I will look into OpenVPN. My drive is relatively quiet, but just knowing that it's constantly being accessed more than once a second is just too much for me to bear.
I had been considering the effects on SSD, but I'm not sure if it's detrimental considering the small amount of data being written.
There are twenty four hours in a day, each with 60 minutes, and each of those with 60 seconds. So that is 24 * 60 * 60 = 86,400 seconds in a day. If it wrote just one time per second, the minimum amount of writes is 86400 * 4096 bytes. That is 353,894,400 bytes, or 337.5 MB of writes every day. And in a year, that is over 120 terabytes of data written.
Your SSD may be mostly full, in which case the same blocks may be written to an abnormal amount of times. And without a doubt, if you use TLC NAND the drive will start reporting bad sectors years faster than it would otherwise.
Is this an anomaly with the latest release or has this always been there?
I am not a knowledgable user when it comes to Windows processes so I cannot tell whether this activity is normal or not. However, if something accesses a drive more than once a second, then that seems like abnormal activity.
I don't know if this is something recent as I only began using PIA a few months ago and more recently noticed this activity a few weeks ago when I installed Windows on a mechanical drive.
The first time I heard of it was almost two years ago. And we tried to figure out if there was anything different that would account for it, but that obviously failed.
Anyway, someone try creating the nolog file before starting PIA Manager, and then check if it still logs.
Now that does make sense (I had never heard of write caching before), but Killswitch claims he can hear the drive constantly clicking which implies it is actually writing to the drives.
It is possible that he has write caching turned off. I just checked my drives and it is turned on (the default).
Currently, PIA does not support advanced encryption settings for OpenVPN.
http://imgur.com/QNahCpr
for anyone worried about PIA eating in to the life of an SSD and you have a spare data drive hooked up to your computer it might be worth it to do this yourself.
I use a 1GB RAMdisk for my browser cache so I don't get a zillion files taking up space on my hard drive - the RAM is cleared when the computer shuts down. I may shift the PIA temp folder to that same RAMdisk.
With PIA running if i leave the computer untouched for the same amount of time disk activity for both drives never stops. almost all of the disk activity for E:\ is explicitly PIA related. Processes causing disk activity for C:\ are system processes with the PID 4 that on first glance have nothing to do with PIA but I can't account for the reason they would disappear from the disk activity list when PIA wasn't running but would stick around when it is.
Examples:
I only had to wait 3 minutes with PIA off to get this screenshot,
http://imgur.com/1tBG4Co
I waited 20 minutes for things to calm down to take this screenshot. The processes from C:\ that would normally disappear without PIA running just plain never disappear
http://imgur.com/i2JnDXe
Maybe I am worrying too much? I JUST got my first ssd and I don't want to take years off of it's lifetime like omninegro mentioned up there when he did his math.
I disable every last log I can on my system. Not because I think I need to hide the diagnostics from myself, but rather because I never need them unless there is a problem.
Next version of the client should really have an option to disable logging.
In OpenVPN all you need to do is change the *.ovpn file line that says "verb #" where the # is the level of logging to 0. (That is a zero, not a capital O.)
http://openvpn.net/index.php/open-source/documentation/manuals/65-openvpn-20x-manpage.html
Anyone know how to do the same for the PIA client?
Anyways thanks for the help I never knew about windows sym links before and I'm pretty stoked to have learned about them.