Intel SSD 320 80gb Lagging problems?

Recently bought this drive less than a week or so, but everytime i use batch render in maya 2011, it makes it a little laggy with hang ups but it still moves. I used a program to analyze the ssd and it says it seriously needs to defrag stuff. I did, but it's still the same. it only hangs when i do batch renders. what could be the prob? :\


Ohhoho. silly me. sorry if i made you guys face palmed

the hanging started before i even defragged the ssd btw.

 

Don't defrag again. Also, please post a screenshot from the AS SSD benchmark program.

 

80gb has pretty low write speed (upto 45MB/s) due to the low utilization of the parallel flash lanes that the controller is connnected to. Could be related to it.

Again, post a benchmark result (AS or Crystal Disk Mark) and we will be able to comment on that more clearly.


--

 

SSDs don't benefit from defragging, so defragging won't help it. The idea with defragging on hard drives is that if your file is split into 1,000 parts and it takes 10 ms for the hard drive to access the next part (on average), it'll take 10 seconds to jump between parts when opening your files. Defragging brings your whole file together again, so you save that 10 seconds. However, the key is that the hard drive's mechanical parts are the reason it takes 10 ms to jump to the next part of the file if it isn't contiguous. An SSD doesn't have the mechanical parts, so the time to jump to the next of the 1,000 parts is for all intents and purposes zero.

ramgen has a good points, too. I'm not familiar with Maya but if it's writing very large files, a hard drive could theoretically be faster for writing.

 

As said previously, if Maya is write heavy, you could end up at the point where GC can't keep up with the writes making the drive very slow. How full is your drive?

Also, I know it's been said, but do not defrag a SSD, it will only use up more writes which will result in a shorter lifespan for the drive if you do it frequently. Windows 7 disables auto defrag when it detects a SSD for a reason.

CMD and AS SSD benchmarks will help greatly as they will provide a comparison with other benchmarks on the same drive.

 

-----------------------------------------------------------------------
CrystalDiskMark 3.0.1 x64 (C) 2007-2010 hiyohiyo
Crystal Dew World : Crystal Dew World
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]

Sequential Read : 247.949 MB/s
Sequential Write : 93.606 MB/s
Random Read 512KB : 179.140 MB/s
Random Write 512KB : 95.231 MB/s
Random Read 4KB (QD=1) : 12.750 MB/s [ 3112.7 IOPS]
Random Write 4KB (QD=1) : 19.291 MB/s [ 4709.8 IOPS]
Random Read 4KB (QD=32) : 138.580 MB/s [ 33832.9 IOPS]
Random Write 4KB (QD=32) : 60.690 MB/s [ 14816.9 IOPS]

Test : 1000 MB [C: 92.9% (69.2/74.5 GB)] (x5)
Date : 2011/12/20 14:52:56
OS : Windows 7 Home Premium Edition SP1 [6.1 Build 7601] (x64)



sooo, what's it say?

 

If i had to take a guess, i'd say that the fact your drive is 92.9% full will slow things to a crawl in anything write intensive.

 

Great point Tijo ^^^^^
I have read a lot of opinions on SSD's anywhere from 20-50% of the drive needs to be free, i wish I knew that before I purchased one.

 

Opinions differ, but the last time i checked, the numbers were at 30-20% free on the SSD review. You probably won't really see a performance drop unless you start doing something write intensive.

Old article: AnandTech - The SSD Anthology: Understanding SSDs and New Drives from OCZ, but it still explains the problem well enough. If your drive is too full Garbage Collection won't be able to keep up and the scenario described in the article will occur. Give TRIM some time afterwards and you should be back to acceptable performance.