SSD Drives and SQL Server Temp DB

By -

I’m in the midst of specing out a new server and I know that it will have a SSD drive in it on which the operating system and key applications will sit.  The idea came up that this is where I should also put my TempDB. Lightening performance!!!!  Right?

 

After all the literature reports:

 

with striping and short stroking of 10 high-end 15,000rpm hard disk drives performance gains of more than 16× are attainable, resulting in more than 3,000 random reads per second. [*]

 

I am coming to the conclusion that this could be a dumb idea if randomly implemented. There are two main types of SSD Drives:

  • single-level cell (SLC) NAND memory – typical enterprise.
  • multi-level cell (MLC) NAND flash memory – typical consumer, cheaper, slower, as much as 10 times fewer read/writes over its life span

So I looked at the specification of one MLC drive, the Super Talent MasterDrive PX Series 64GB 2.5in SATA II Solid State Drive, SLC NAND Flash and read:

  • Read: Unlimited
  • Write: 350.7 yrs yrs @ 50GB write-erase/day

      So for OS and other stuff – it is sweet. For a TempDB for SQL Server it is definitely not industrial strength – 500 GB of writes/hr into tempDB is not unreasonable so the life expectancy is down to < 2 years. In fact, digging deeper I read:

      one SSD drive has specifications of 130 random writes per second and 18,000 random reads per second, enabling the drive only to maintain a random write rate less than 1% of its read rate. In contrast, hard disk drives can typically maintain write rates close to 90% of their read rates.[*]

      Bottom line is clear: SSD drives are NOT for TempDB. The 16x performance gain could be reduced to 1% x 16 = 0.16 performance gain or SIX TIMES worst performance… Of course, you may find a SSD drive that could work…  but you want at least 16% write rate versus read rate.

      The resulting configuration that I am planning:

      • Core i7 920/930
      • SSD Drive – likely the Super Talent cited above for OS and key applications only
      • 12 Gigs Ram (to start)
      • Raided SATA drives

      Comments

      Post a Comment

      Popular posts from this blog

      Simple WP7 Mango App for Background Tasks, Toast, and Tiles: Code Explanation

      By -
      Image
      This is a continuation of this post , explaining how the sample app works. Caution : This sample isn’t meant as an example of best patterns and practices. If you see something in the code you would never do, then don’t. Solution File Organization The app has three Visual Studio Projects: the app, the agent, and the shared code library between them. One of the great things about Mango is that now the built-in Visual Studio Unit test functionality is available. By separating out the meat of the work into the SampleShared project, I can also focus my unit testing there. SampleApp1 The app has a MainPage, a ViewModel, and the WMAppManifest.xml file modified to note my ExtendedTask of BackgroundServiceAgent. The Agent is extremely simple with a call to the shared library, an update to the Tile, and a call to pop up Toast. The meat of the work is in the SampleShared library. The AgentMgr manages the background agent : add, remove, find, run now. It is only called f...
      Read more

      Yet once more into the breech (of altered programming logic)

      By -
      Once upon a time, long long ago, I wrote 8-bit programs in Tiny-C with absolute addressing being the only reality.  Then we had Borland Turbo-C with relative addresses and the joys of relative assembly jumps. Enter Windows and the joys of locking and unlocking memory blocks that you must allocated and manage yourself. Then came Visual Basic which evolved into .Net CLR and decreasing awareness of what is happening under the hood.   With VS2010 including F# and enhanced parallelism in .Net4, we actually have to go retro a bit – back to the world of having to understand the hardware. CPU speeds are no longer increasing – I have an old laptop from six+ years ago that ran at 3.2 GHz. This year I updated one of my machines off-the-shelf from Costco.com, an I7-920 with 4 cores and hyper-threading (8 CPUs appears in Task Manager) and 12 GB of DDR3 RAM. This week I ordered from Costco a Phenom II X6 (Yes – 6 REAL CORES) for one of my daughters.  This CPU will (according to Yo...
      Read more

      Error : /ScriptResource.axd : Invalid viewstate.

      By -
      This issue is caused when the ScriptResource.axd querystring parameters can not be decoded on the server. This error can be caused from multiple issues with server configuration or the Browser's interaction with the server. The ScriptResource.axd contains all of the clientside javascript routines for Ajax. Just because you include a scriptmanager that loads a script file it will never appear as a ScriptResource.AXD - instead it will be merely passed as the .js file you send if you reference a external script file. In other words it is what the Microsoft Ajax libraries inject into your HTML to allow them to access their javascript functions they need for page manipulation. ASP.NET will use the machine key to encrypt the ScriptResource.axd (and webresource.axd) url's parameters(in querystring), and by default the machinekey is a randomly generated one which may involve the current time. By default there is a different machinekey on every machine, and it changes when the applic...
      Read more