These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

SSD workaround for EVE Odyssey issue on logfiles and cache

Author
Tessle Aesis
Leones Aesis
#1 - 2013-06-06 10:52:39 UTC  |  Edited by: Tessle Aesis
TO ALL USING A SSD HAVING LOW-FPS ISSUE WITH ODYSSEY

Odyssey get crazy if you prohibited (to prevent SSD degrade) EVE to access logs directory, with Odyssey it seems it wants to write those logs and send the OS tons of request causing high CPU usage 2x or 3x times than before Odyssey and dropping down FPS rate to 4. TO AVOID THIS YOU MUST ALLOW EVE TO WRITE LOG FILES, at least this until CCP release a fix, if they'll do.


WORKAROUND FOR WINDOWS 7 USERS to have EVE happy with logfiles and your SSD safe from the degrade logfiles could cause:

- PvPers: consider use of RAMDRIVE speedup all the processes specially during large combat!

like suggested by CCP Habakuk:

CCP Habakuk wrote:
Tessle Aesis wrote:
Lursider wrote:
yup, I was preventing eve writing on my SSD (you know why ...).

I removed this restriction and now everything work fine !!!!

by the way, is there a way to stop this perpetual writing ?


WTF ?

i've also blocked EVE to write some cache directories, just because i take care of my SSD... I've also one 1Tb HDD

1) CCP could you please STOP this perpetual and stupid write,
2) or LET US CHOOSE the PATH where to store the cache?!

I'm about to let again EVE to write in my SSD, if it was the problem with the poor performance 4 FPS, i'll be very angry, with you CCP of course.

I will not play a game which will seriously degrade mt SSD840 PRO 240Gb performance!
so do something about this, 1 or 2.


I cannot give you an official answer at the moment, but maybe following workaround might help you: For 2) you can redirect the logs to a folder on your HDD by using a symlink. This is also not really officially supported (as far as I can tell), but it seems to work and I cannot see any drawbacks so far (I am sure, that anybody will correct me on this).



to prevent EVE doing tons of write access to your SSD use a Symlink. Here you can find 3 guides that explains how it works and how to create a simlink.

http://lifehacker.com/5496652/how-to-use-symlinks-in-windows
http://www.tested.com/tech/windows/39-using-symlinks-in-windows-for-fun-and-profit/
http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

of course you need an HDD as 2nd storage drive or in the case your PC has only the SSD then you need to install a RAMDRIVE program, that is also usefull to prevent furthermore SSD degrade by associating both User & System TEMP to it (I've put pagefile too into Ramdrive).

by having these requisites (a 2nd HDD or a RAMDRIVE) now you can symlink your folder Documents\EVE\logs to a path out of your SSD, see the example below, supposing to have a unit (HDD or RAMDRIVE) named T: (of course change T: with your driver identification letter)

run CMD.EXE (better if do it with "Run like Administrator") then give these commands:

MD T:\EVE
MD T:\EVE\logs
%systemdrive%
CD "%systemdrive%\Users\%username%\Documents\EVE"
RD /S /Q logs
mklink /j "%systemdrive%\Users\%username%\Documents\EVE\logs" T:\EVE\logs

if you have an HDD (example T: is an HDD) you have done! else continue...

ONLY FOR RAMDRIVE USERS:
the problem with RAMDRIVE is you have to recreate the directory in your drive T: each time you restart the PC (because of course those folders went lost when you restart the PC). You can do it with a batch file

run NOTEPAD.EXE and write the code:


MD T:\EVE
MD T:\EVE\logs

then save the file in your desktop, naming it: EVELOGS.BAT
copy it into your StartUp directory, you can use one of the following the CMD commandline:

1) this is only for your account:

COPY "%systemdrive%\Users\%username%\Desktop\EVELOGS.BAT" "%systemdrive%\Users\%username%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup"

2) if you want this to all your accounts use this command instead:
COPY "%systemdrive%\Users\%username%\Desktop\EVELOGS.BAT" "%systemdrive%\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup"

EXIT

YOU HAVE DONE

---

ALSO some SSD users prevents EVE to write pictures (chat avatars etc) into the cache, other lots of files, doing this you don't see any avatar pictures in chat or in station, could be sad or disappointing, but your SSD is safe and you got much more speed in high populated systems.

You can now extend what seen above to recreate these folders with pictures in your HDD or RAMDRIVE (RAMDRIVE is suggested) so You can see again pictures and have SSD happy at same time:

run CMD.EXE (better if do it with "Run like Administrator") then give these commands:

MD T:\EVE\char
%systemdrive%
CD "%systemdrive%\Users\%username%\AppData\Local\CCP\EVE\c_program_files_(x86)_ccp_eve_tranquility\cache\Pictures"
RD /S /Q Characters
mklink /j "%systemdrive%\Users\%username%\AppData\Local\CCP\EVE\c_program_files_(x86)_ccp_eve_tranquility\cache\Pictures\Characters" T:\EVE\char

Again if you do it on an HDD you have done, in the case you use a RAMDRIVE now you have to update the EVELOGS.BAT files created before, you could only update the one in StartUp Menu: access your Start, Programs, StartUp, right-click on EVELOGS.BAT and click Modify

then at the end add this line


MD T:\EVE\char

SAVE the file (relaunch EVELOGS.BAT) or restart the the PC and You have DONE!

---

now that you know how it works... good work :)
of course a fix from CCP regarding how EVE's logs and cache are stored is welcomed...


flysafe SSDsafe

Tessle Aesis
Woo Doggy
Doomheim
#2 - 2013-06-07 20:22:15 UTC
What the heck? Is this even English?
S'No Flake
Native Freshfood
Minmatar Republic
#3 - 2013-06-08 20:28:05 UTC  |  Edited by: S'No Flake
I don't know if it is a good idea to put this here Pirate

WARNING: use this ONLY if you understand what it does!

This is the code used inside the application:

Quote:

#!/bin/bash

if [ ! -d /Volumes/Logs ]
then
echo "Creating RamDisk..."
diskutil erasevolume HFS+ 'Logs' `hdiutil attach -nomount ram://1048576`
echo "Done!"
else
echo "RamDisk already mounted!"
fi


if [ ! -d /Volumes/Logs/EVE ]
then

echo "Creating EVE Folder..."
mkdir /Volumes/Logs/EVE
echo "Done!"
else
echo "EVE folder already created..."
fi


if [ ! -d /Volumes/Logs/EVE/logs ]
then
echo "Creating Logs folder..."
mkdir /Volumes/Logs/EVE/logs
echo "Done!"
else
echo "Logs folder already created..."
fi


if [ ! -L ~/Library/Application\ Support/EVE\ Online/p_drive/User/My\ Documents/EVE/logs ]
then
echo "Moving logs to RamDisk..."
mv ~/Library/Application\ Support/EVE\ Online/p_drive/User/My\ Documents/EVE/logs ~/Library/Application\ Support/EVE\ Online/p_drive/User/
ln -s /Volumes/Logs/EVE/logs ~/Library/Application\ Support/EVE\ Online/p_drive/User/My\ Documents/EVE/logs
echo "Done!"
else
echo "Logs aleardy on RamDisk..."
fi




It will create a 512Mb ram disk, backup your existing logs folder and create a symlink to the ram disk.
It will work only of you use the default EVE location.
You will have to run it every time you play Eve other way, the symlink will point to a non existing folder... which might be bad :)


WARNING: when you reboot or eject the ram disk:
- you will loose all the logs created
- you will also LOOSE ALL THE DATA you put on the ram disk


Again, DON'T TOUCH THIS if you don't know what the script does.

App Arrowhttp://eve-files.com/dl/262965
Nuran Mukadder
Chor Aurea
#4 - 2013-06-08 21:34:12 UTC
Maybe I'm wrong, but wouldn't a deferred write-back cache be simpler and more practical? Everything stays in memory until shutdown or idle processor time, so several writes should be coalesced into a single write burst.

Here's a simple guide: http://www.howto-connect.com/enable-or-disable-disk-write-caching-in-windows-8/

I'm on a Windows 8 machine, EVE installed on a 128GB SSD and having no issues at all. Didn't tried to turn this setting off, though.
Bombcrater
The Scope
Gallente Federation
#5 - 2013-06-08 23:40:11 UTC
Tessle Aesis wrote:
Odyssey get crazy if you prohibited (to prevent SSD degrade) EVE to access logs directory

There is absolutely no need to do this. SSDs are designed to be able to deal with gigabytes worth of writes every single day for years on end.

The wear-leveling code in the firmware of current SSDs is generally so good that you can just treat them like hard drives and edurance of the flash chips is not an issue. it's almost impossible to wear out the drive without actively hammering it for months with a workload specifically designed to kill it.