using a SSD with Visual Studio ... setup?
-
10 minutes down to 40 seconds? Then there was something seriously wrong with your 7200 rpm disks.
-- Kein Mitleid Für Die Mehrheit
Based on what?
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
10 minutes down to 40 seconds? Then there was something seriously wrong with your 7200 rpm disks.
-- Kein Mitleid Für Die Mehrheit
-
My new work machine will come in soon. One of the feature that I have asked and obtained is a SSD drive. :-D What is the best practice when using a SSD drive and Windows 7 and Visual Studio (2008, 2010, 2012) and mostly/mainly C++ code ? Have the OS, "Program Files" all on the SSD and the project files (project solution, source files) as well ? And all the data on another drive ? Thanks.
Watched code never compiles.
In addition to the improved build speeds, I find Search/Replace across large solutions MUCH faster with an SSD. I can search the entire code base almost instantly, whereas accessing thousands of files on a HDD can be seriously underwhelming. So on my SSD I have Windows, Apps, VS2010, and my VS solutions and code. Robert
-
My new work machine will come in soon. One of the feature that I have asked and obtained is a SSD drive. :-D What is the best practice when using a SSD drive and Windows 7 and Visual Studio (2008, 2010, 2012) and mostly/mainly C++ code ? Have the OS, "Program Files" all on the SSD and the project files (project solution, source files) as well ? And all the data on another drive ? Thanks.
Watched code never compiles.
We found that putting the working copies of our projects on the SSD and the OS on the HDD gave us very good performance all-round. Windows 7 with enough RAM (we have 8g) will cache much of the oft used parts of the OS and Visual Studio in memory anyway, and you still get the reliability of a HDD. One of our guys experimented with the swap file (I don't remember if he did something like a RAM drive, or what; he's not here anymore to ask) that had the effect of putting it in memory, that sped things up even more, but nobody else has done that. The working copies on the SSD are pretty fast, but as others noted, the most significant speed up is when doing a full build. Incremental ones don't benefit as much. However, all the other ancillary operations, searching, checking out, checking in, etc, are faster as well. Putting ony non-critical stuff on the SSD reduces the risk of downtime due to a, fortunately much less frequent these days, failure of the SSD.
Currently reading: "The Prince", by Nicolo Machiavelli
-
My new work machine will come in soon. One of the feature that I have asked and obtained is a SSD drive. :-D What is the best practice when using a SSD drive and Windows 7 and Visual Studio (2008, 2010, 2012) and mostly/mainly C++ code ? Have the OS, "Program Files" all on the SSD and the project files (project solution, source files) as well ? And all the data on another drive ? Thanks.
Watched code never compiles.
I have an SSD in my machine, but use a 7500 rpm for code storage. I do tons of Chromium development (the browser) and a normal build with 695 projects takes roughly 4 hours. When I get home, I'll drop the code on my ssd and run a compile. there are TONS of disk I/O operations during the build. I'll post up my results for you all to use as a reference.
-
My new work machine will come in soon. One of the feature that I have asked and obtained is a SSD drive. :-D What is the best practice when using a SSD drive and Windows 7 and Visual Studio (2008, 2010, 2012) and mostly/mainly C++ code ? Have the OS, "Program Files" all on the SSD and the project files (project solution, source files) as well ? And all the data on another drive ? Thanks.
Watched code never compiles.
Actually I have all my OS, programs, VS, solutions, personal data files, music... basically everything on my SSD; but I do a backup of all the important stuff to a NAS every night (VS files and solutions) and a full drive back up to my secondary HD once a week, just in case the SSD decides to dump. But WOW you can't beat the SSD speed.
-
For my money, ANYTHING to speed up your work computer is worthwhile. The most expensive part of a PC is the operator! Also, each time a developer is interrupted (phone call, email, announcement, etc.), it takes about 20 minutes to get back up to speed. So, if a 30-second compilation does not interrupt you, but a 10-minute one does, you're talking about taking a 30-minute interruption, or probably about $50 charged. I'd say in a couple of days you'd pay for that SSD!
The end justify the means… :laugh:
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
Based on what?
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
Because my own measurements show a speedup between 2x to 4x, when going from a 7200 RPM SATA disk to a 6 Gbps SSD (OCZ Vertex 3, Sandy Bridge). Consistently so on at least three machines. A 15x speedup sounds unreal to me, unless there was something very wrong with his previous disk.
-- Kein Mitleid Für Die Mehrheit
-
We found that putting the working copies of our projects on the SSD and the OS on the HDD gave us very good performance all-round. Windows 7 with enough RAM (we have 8g) will cache much of the oft used parts of the OS and Visual Studio in memory anyway, and you still get the reliability of a HDD. One of our guys experimented with the swap file (I don't remember if he did something like a RAM drive, or what; he's not here anymore to ask) that had the effect of putting it in memory, that sped things up even more, but nobody else has done that. The working copies on the SSD are pretty fast, but as others noted, the most significant speed up is when doing a full build. Incremental ones don't benefit as much. However, all the other ancillary operations, searching, checking out, checking in, etc, are faster as well. Putting ony non-critical stuff on the SSD reduces the risk of downtime due to a, fortunately much less frequent these days, failure of the SSD.
Currently reading: "The Prince", by Nicolo Machiavelli
one word. Sexy
-
My new work machine will come in soon. One of the feature that I have asked and obtained is a SSD drive. :-D What is the best practice when using a SSD drive and Windows 7 and Visual Studio (2008, 2010, 2012) and mostly/mainly C++ code ? Have the OS, "Program Files" all on the SSD and the project files (project solution, source files) as well ? And all the data on another drive ? Thanks.
Watched code never compiles.
SSD is a dog. Definitely in ideal case it works faster, but since product of stupid Gates permanently writes cr@p on disk (emulating robustness), your poor SSD will indefinitely reallocate sectors to write every portion of data. What, as you guess, will decrease perfomance. Second issue is reliability - after year your SSD will go slower and slower - again thanks stupids from MS. So best practice is using SSD in scenario "write once, many reads", like DVD or strimmer. :)
-
Because my own measurements show a speedup between 2x to 4x, when going from a 7200 RPM SATA disk to a 6 Gbps SSD (OCZ Vertex 3, Sandy Bridge). Consistently so on at least three machines. A 15x speedup sounds unreal to me, unless there was something very wrong with his previous disk.
-- Kein Mitleid Für Die Mehrheit
I think it may vary a lot, specially because SSDs perform differently depending on file sizes and block sizes. In OPs particular case, the project was quite big (28 projects :wtf: ). I think it could actually outperform magnetic disks in that scale, specially because fragmentation is a much bigger issue in that case.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
I think it may vary a lot, specially because SSDs perform differently depending on file sizes and block sizes. In OPs particular case, the project was quite big (28 projects :wtf: ). I think it could actually outperform magnetic disks in that scale, specially because fragmentation is a much bigger issue in that case.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
I had > 28 projects (around 35 or so), and there was no such speed up.
-- Kein Mitleid Für Die Mehrheit
-
My new work machine will come in soon. One of the feature that I have asked and obtained is a SSD drive. :-D What is the best practice when using a SSD drive and Windows 7 and Visual Studio (2008, 2010, 2012) and mostly/mainly C++ code ? Have the OS, "Program Files" all on the SSD and the project files (project solution, source files) as well ? And all the data on another drive ? Thanks.
Watched code never compiles.
Have a look at this: win7-how-do-i-move-user-folder-to-a-different-drive It has been considered a good idea to move folders with files with frequent changes away from the SSD to reduce the erase-write-cycles and to expand its lifetime . Additionally I installed a free Ramdisk(RAM is cheap) and set the TEMP-folders to it. mlinking every folder with volatile data to it seems like an interesting idea, too :)