Page 3 of 14 FirstFirst 1234513 ... LastLast
Results 21 to 30 of 140

Thread: M28 Windows 7, FirmWare, TRIM, Optimizations, Etc...

  1. #21

    Default

    Very nice, thanks for taking the time to share.

  2. #22
    Join Date
    Nov 2009
    Posts
    133

    Default

    hey magic what about this
    There are some other more advanced things I do, but to be honest, they result in very little speed increase (less than 1%).
    please share

  3. #23
    Join Date
    Dec 2009
    Location
    Trinidad
    Posts
    139

    Default Services...

    Quote Originally Posted by obamaliar View Post
    hey magic what about this
    There are some other more advanced things I do, but to be honest, they result in very little speed increase (less than 1%).
    please share
    Some of what I do is not limited to SSD, but overall OS optimization...
    Services... I used the black viper guide and got mine trimmed down some without losing functionality of Win 7... I like it the way it is (almost). U can read up on what each service does and decide for yourself...
    http://www.blackviper.com/Windows_7/servicecfg.htm

    However, here are the services on my machine (laptop):
    w7srvcs.txt
    Tab separated file with MY service config...

  4. #24
    Join Date
    Dec 2009
    Location
    Trinidad
    Posts
    139

    Default SSD Virtuilization Tips...

    I use VMWare all day long on my SSD and have found a few little tricks to make it run smoother with less writes to the SSD.
    My host is Windows 7 64-bit. My VMs are mostly XP pro andd home (and a Server 2008R2)....

    Basically, the tips are as follows and assume you are running VMWare:
    With the exception of the page file, follow the tips for configuration in the VM as you would if it was the host OS. Even in a VM, a page file is needed (to a point). Just google things like XP SSD tips, etc.

    If you have 2 drives (The SSD and a normal HD), then you can really pump up the speed of the VM if you are running it off the SSD...
    1) In the VM settings, create a new virtual drive. Put it on the normal Hard drive (I set mine to 1 gig). Inside the VM, set the new virtual drive as the VMs page file drive. This off-loads a lot of writes to the normal hard drive without really affecting performance.

    2) (advanced) Did you know you could run a VM in an almost read-only state from the SSD? Did you know that you can have a VM reading from both drives at the same time during VM boot and operation and writing to the HD only without raid? Basically, we can use the snapshot feature in VMWare to create a fake raid setup for each virtual machine:
    In the VMX file for the VM, we need to edit/add the line
    workingDir = "E:\VMWare Images\XP Home Personal SnapShot\"
    where the directory is where you will be storing the snapshot on the spinner.
    In the settings for the VM in VMWare, make sure to uncheck "independent" under advanced options for the virtual hard disk on the VM.
    Click on VM up top then create snapshot. As of that point on, all the writes will go to the snapshot file on the spinner and all the reads will come from both.
    There is a trade off after a while... Since all writes to the VM drive (snapshot) are block level writes, the more you use the VM, the less performance gain U will get (more and more reads will come from the snapshot file). To prevent that, I merge the snapshot file once a week or once every 2 weeks to the VM on the SSD.

    Also, to save space on the SSD, I only put my most used VMs on the SSD (the 2 that are used all day).

  5. #25
    Join Date
    Nov 2009
    Posts
    133

    Default

    hey magic, i need your knowledge. i bought another brand ssd drive speed:
    --------------------------------------------------
    CrystalDiskMark 2.2 (C) 2007-2008 hiyohiyo
    Crystal Dew World : http://crystalmark.info/
    --------------------------------------------------

    Sequential Read : 208.120 MB/s
    Sequential Write : 100.182 MB/s
    Random Read 512KB : 182.952 MB/s
    Random Write 512KB : 120.250 MB/s
    Random Read 4KB : 32.735 MB/s
    Random Write 4KB : 11.880 MB/s

    Test Size : 100 MB
    Date : 2010/02/26 22:08:44

    i bought it to be the paging file for my torqx how should i do it? make a seperate small partition on it like 9gb or what do you think? or just put the paging file on it and let windows manage the size? do you know if its possible to put the prefetch and superfetch from my os (torqx) onto the vertex?
    Last edited by Patriot_Ben; 03-08-2010 at 06:24 PM.

  6. #26
    Join Date
    Dec 2009
    Location
    Trinidad
    Posts
    139

    Default

    Quote Originally Posted by obamaliar View Post
    hey magic, i need your knowledge. i bought a 30gb ocz vertex speed:
    --------------------------------------------------
    CrystalDiskMark 2.2 (C) 2007-2008 hiyohiyo
    Crystal Dew World : http://crystalmark.info/
    --------------------------------------------------

    Sequential Read : 208.120 MB/s
    Sequential Write : 100.182 MB/s
    Random Read 512KB : 182.952 MB/s
    Random Write 512KB : 120.250 MB/s
    Random Read 4KB : 32.735 MB/s
    Random Write 4KB : 11.880 MB/s

    Test Size : 100 MB
    Date : 2010/02/26 22:08:44

    i bought it to be the paging file for my torqx how should i do it? make a seperate small partition on it like 9gb or what do you think? or just put the paging file on it and let windows manage the size? do you know if its possible to put the prefetch and superfetch from my os (torqx) onto the vertex?
    Hmmmmmmmmmmmmm..... Kinda overkill, since I recommend having the page file on the OS drive, BUT..... Since the second drive IS an SSD, I would say go ahead and put the paging file on it to free up some space on your boot drive. More free space on an SSD allows wear-leveling to work better.

    As for the superfetch and prefetch stuff... Although I fully recomend turning it off via the instructions in the tutorial, IF you found performance to actually be better with it on (rare, but in some configurations it is faster to leave it on)... we CAN move the prefetch folders off the boot drive onto the second drive using windows 7 junctions. Basically, it is a pointer to a location so Windows thinks the directory is still there, but it is actually somewhere else...

    It could pose some issues later, though... Is this what you want to do?
    Perhaps it is time for my tutorial on how to move un-neccessary stuff to the other drive and fool Windows into going there?

    What U think?

  7. #27
    Join Date
    Nov 2009
    Posts
    133

    Default

    i value your opinion so........ what would you do with what ive got? i bought another brand drive new for $ 123.00 and it has a $ 40.00 rebate so i couldn't pass it up. i havent used a paging file in a couple of years but if you say its better to have one then i feel better about putting it on the vertex cause i dont care if i wear it out it was so cheap. as for prefetch and superfetch im not sure if they make any difference i dont have them turned on. my new system is so fast with this core i7 930 at 4ghz its already mind blowing
    Last edited by Patriot_Ben; 03-08-2010 at 06:24 PM.

  8. #28
    Join Date
    Nov 2009
    Posts
    133

    Default

    Perhaps it is time for my tutorial on how to move un-neccessary stuff to the other drive and fool Windows into going there?

    What U think?

    YES!

    It could pose some issues later, though... Is this what you want to do?
    What kind of issues?

  9. #29
    Join Date
    Dec 2009
    Location
    Trinidad
    Posts
    139

    Wink

    Quote Originally Posted by obamaliar View Post
    Perhaps it is time for my tutorial on how to move un-neccessary stuff to the other drive and fool Windows into going there?

    What U think?

    YES!

    It could pose some issues later, though... Is this what you want to do?
    What kind of issues?
    Ok.... The next addition to the guide will be moving parts of Windows to another drive along with the possibility of seperfetch / prefetch....

  10. #30
    Join Date
    Dec 2009
    Location
    Trinidad
    Posts
    139

    Red face Moving parts of Windows 7 to another drive...

    It has been asked what other little things can be done to squeeze a litle more performance from Windows 7 on our SSD drives... One thing that helps maintain performance on an SSD is the percentage of free space available to the SSD controller to execute 'wear leveling'. Basically, spreading out the load to the least used empty memory cells.
    In order to do this, we need to fool Windows and other programs into looking elsewhere for stuff that is necessary, but rarely used and taking up a lot of disk space.
    This part is only useful IF you have your operating system on your SSD AND it is formatted as NTFS and have a second drive available (NTFS) with space free to use.
    What we are going to do is move certain directories to the other drive, then make Windows (and the programs) think it is still on the boot drive. We do this by using an NTFS 'junction'. Think of a junction as a pointer to a location. To the operating system, the files look like they are in location A, but they are really physically in location B.

    For the tutorial, we are going to assume that the SSD is C: and the second drive is E:. Substitute your drive letters as needed. As always, MAKE A BACKUP FIRST!
    If you are still with me, here is how to do it (the easy way):
    Go to http://schinagl.priv.at/nt/hardlinks...kshellext.html and download (and INSTALL) the link shell extension software (and VC runtime, follow the instructions on the site) for your flavor of Windows 7 (or barf Vista).
    Make sure explorer is set to SHOW hidden and system files (Tools/Folder Options/View tab, Show hidden, uncheck Hide protected operating system and hide extensions)
    Create the following directories:
    E:\WinSystem
    E:\WinSystem\Windows
    Boot into safe mode. Open explorer and navigate to C:\Windows.
    Right click on the Installer directory and select CUT
    Navigate to E:\WinSystem\Windows right click and select paste. It should have created the directory E:\WinSystem\Windows\Installer with files in it.
    Right click the directory E:\WinSystem\Windows\Installer and select Pick Link Source.
    Navigate to C:\Windows and right click in the directory and select Drop As and select Junction.
    You should now see C:\Windows\Installer is back (with a wierd link on the folder icon)... The OS now will put installer files on the other drive and look for them there, but think it is still on c:!
    Other directories I do this with are the HP install directory (C:\SwSetup) and MS Office setup directory (C:\MSOCache).
    In the previous tutorials, yo learned how to move the TEMP and internet Temporary files... This is a good place for them too. Here is the directory structure on my E:\WinSystem directory:
    E:\WinSystem\MSOCache
    E:\WinSystem\SwSetup
    E:\WinSystem\Temp
    E:\WinSystem\Temporary Internet Files
    E:\WinSystem\Windows\Installer

    Just make sure to drop the junction in the same place as the original directory and the OS will be none the wiser and you will have moved GIGABYTES of seldom used stuff of your SSD (and redirected some more writes)!

    The only down side that I have found is as follows: If your backup strategy is like mine WAS, then you would only be making a backup image of the SSD. The problem is, that image backup software does not see that you moved the files, so they cannot copy the files in the E:\WinSystem directory with the image. The fix is quite simple if U are using Windows 7 backup: Along with the system image, have it back up the directory E:\WinSystem. Then it will keep them together and in sync (you restore the image AND the directory that went with the image).

    Undoing the junction is easy too, if you want to. Simply delete the junction from the C drive and move the directory back where it was (hence the reasoning I had you create WinSystem\Windows\Installer instead of WinSystem\Installer as a reminder of where the directory was when U started!
    Last edited by magic-man; 03-14-2010 at 06:11 AM.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •