Vertex 3 not running fast anymore

[Bossboss]

Had my Vertex 3 120gb for about 2 weeks now, and it has slowed down quite a bit.

When I first got it, Xbench scores were around 500, and AJA System Test gave me around 500/500 mbps read/write.

Now my Xbench scores are around 420, and AJA System Test gives 380/380 mbps.

I do not have TRIM enabled; I had it enabled a while ago, but it caused beachballing so I turned it off.

Also I thought it could be a software issue, so I JUST reformatted OSX and still getting the same scores...

What can I do to get it back up to 500/500???? The drive is only 20-30% full. Anyone experiencing this problem? Is there a solution?

Thanks!

 

[PAPO]

is it an early 2011 model? if so read on if not ignore the rest of what I've written

now that I recently had what seems as a catastrophic HDD failure as I look back I see in the days leading up my computer had been getting slower and slower, so FOR THE LOVE OF GOD BACK UP NOW, as my hypothesis forms as to what has caused this I and starting to think it may have something to do with the Cougar Point chipset manufacturing issues reported only weeks before the newest MPB's released

(yes I know it only affected the 3Gb/s SATA ports and not the 6Gb/s port the HDD uses but it could be vaguely related)

 

[Bossboss]

is it an early 2011 model? if so read on if not ignore the rest of what I've written

now that I recently had what seems as a catastrophic HDD failure as I look back I see in the days leading up my computer had been getting slower and slower, so FOR THE LOVE OF GOD BACK UP NOW, as my hypothesis forms as to what has caused this I and starting to think it may have something to do with the Cougar Point chipset manufacturing issues reported only weeks before the newest MPB's released

(yes I know it only affected the 3Gb/s SATA ports and not the 6Gb/s port the HDD uses but it could be vaguely related)

it's 2011 15" 2.2 8gb ram. it's got nothing to do with a harddrive failure.

i feel like it has something to do with not having TRIM enabled. When i had trim enabled i reached 500mb/s easily but at the cost of beachballing on occasion.

I'd like to hear from people who have a vertex 3 on the new mbp's and don't have trim enabled.

 

[NickZac]

It shouldn't be slowing down due to issues such as 'degration' given current flash memory does not have these issues as people emphasize; furthermore, the SF controllers and wear leveling software should prevent the 'clutter' people speak of (ha!).

You may not have an issue though, as XBench is archaic and not designed for SSDs, let alone SSDs that are SATAIII. Even more modern bench tests seem to do fluky things with SSDs that are SF2k driven. Do you see a slowdown yourself?

 

[DarkFlame]

Had my Vertex 3 120gb for about 2 weeks now, and it has slowed down quite a bit.

When I first got it, Xbench scores were around 500, and AJA System Test gave me around 500/500 mbps read/write.

Now my Xbench scores are around 420, and AJA System Test gives 380/380 mbps.

I do not have TRIM enabled; I had it enabled a while ago, but it caused beachballing so I turned it off.

Also I thought it could be a software issue, so I JUST reformatted OSX and still getting the same scores...

What can I do to get it back up to 500/500???? The drive is only 20-30% full. Anyone experiencing this problem? Is there a solution?

Thanks!

That sucks, I hope it does not happen to me. I've had it for 2 weeks and it has not slowed down. Only 30% full, no trim enabled as well. Sounds like your drive is bad? Can anyone else chime in?

 

[JasonH42]

That sucks, I hope it does not happen to me. I've had it for 2 weeks and it has not slowed down. Only 30% full, no trim enabled as well. Sounds like your drive is bad? Can anyone else chime in?

Hmmmmmmm...so...380MB per second is not fast, bad and sucks?

Well, you could return the drive and go back to a regular platter.

Or, you could stop running benchmark software (and leave TRIM off as it causes beachballing) and just enjoy your blazing fast SSD?

 

[Bossboss]

Issue is resolved:

Apparently the tests I was doing in AJA had different settings.. I just chose the last option now and ran the SSD benchmark, 500/500. Previously I was just running the default Video Frame Size of 720x486.. which I'm guessing is less compressible than the last option of 2048x1556, thus slower read/write.

I totally forgot that SSD speeds depend on the compressibility of the files.

 

[pedrofan]

Issue is resolved:

Apparently the tests I was doing in AJA had different settings.. I just chose the last option now and ran the SSD benchmark, 500/500. Previously I was just running the default Video Frame Size of 720x486.. which I'm guessing is less compressible than the last option of 2048x1556, thus slower read/write.

I totally forgot that SSD speeds depend on the compressibility of the files.

I got the same results with mine.