Quote Originally Posted by Ao1 View Post
@ groberts101

#1 question According to my guestimates in post #27 you will need to write at least 10.75GB per "power on hour" to see throttling in the form I have experienced. You are nowhere close to that based on your SMART data. (I actually wrote ~28,352 GB in 168 power on hours)

#2 If a SE has restored the performance of that particular drive it is unlikely it had anything to do with this form of throttling that I have experienced.

#3 Also throughout running Anvils app there was not a significant slow down in performance. Overall performance was constant UNTIL throttling kicked in. When that happened write speeds dropped very quickly. (Over a few seconds)

#4 Now you might say that for whatever reason my numerous attempts to SE using three different apps across 2 PC's was a failure.

#5 Here is the kicker. Immediately after a SE write speeds were throttled. If the drive was degraded or throttled because the SE failed, why were speeds restored with nothing more than 1 hour of idle time?
sigh.. I'm trying very hard to stay with you here but you seriously need to stop thinking that you have this controller figured out here. Wipe some of the slate clean and you will be much further ahead.

It seems that I'm just repeating myself constantly. There are some known facts about these controllers and any other findings are pointing to user error or just plain bad "fact finding". Not trying to be ty at all and simply have limited time and often shoot from the hip with my responses so absolutley no offense is intended. Lets just drop the ego and pride out of it and use some facts that have been proven by many. IOW's,.. let's just make it about figuring out the issue with your drive and cut through all the other crap.

from above quote:

#1 QUIT GUESSTIMATING OFF THESE FIGURES! seriously dude... they have absolutley NOTHING to do with the "settled state" throttles(which is my preferenced term over the "lifetime thottle" being used for these drives. I already expalined it over on OCZ forums for you. Tony helped my figure most of this crap out by testing and studying them right along beside me with me being the "Terabytes of incompressible data written" guinea pig for many others. Hundreds upon hundreds have cleared their drives with an SE and is SOP when issues or heavy throttles(hammered state) arise.

And to be clear here.. I have had my drives(singles and arrays) throttled to all known stages(which I've also explained previously, as well). SE recovers/restores factory fresh speeds each and EVERY time. I may have passed the 100 SE mark but lost track long ago when I often did 7-8 per day when heavily testing them. I know these drives internal algorithms like a bad dream and even know EXACTLY when settled states hit my array. Not to be confused with hammered states. Small lags when heavily multitasking(and I mean HEAVY) and even logoffs/logons/shutdowns/reboots can be measurably longer by about 10 seconds.

It's like clockwork(settled states hitting me) and an SE/reimage(even using the same saved image as currently in use since I did try and exclude the old used W7 install as the culprit) will bring me back to fresh speeds with well over 100MB/s incompressible write speeds. After all.. I should know by now when my video transfers are down by that much, right?

#2 not even a remote possibility as I know my drives and their limitations very well for some of the reasons listed above in #1.

#3 This is where you are having difficulty getting your head wrapped around the stages of throttle on this controller. That massive slowdown would be considered a "hammered state throttle" and NOT a settled state. A settled state throttle will limit incompressible write speeds to about 70% of fresh speed. Hammered states would be about 50% of fresh when writing incompressible data. Why you are getting the drive drops way down to that 6-7MB/s range?.. I have no idea but can help you to more effectively test within the parameters of the lifespan test you are trying to achieve in the other thread.

Would need a lot more trust and opening of the mind before that would be possible, though. I am seriously interested in those endurance tests and coming around here(even trying over on the OCZ forum with you) to help and post what I know has nothing at all to do with trying to strut around and show off my Sandforce understanding. It's far more to do with what I think of myself and the need to share.. than what anyone else thinks of me as I;m not nearly that shallow. If you and everyone else keep putting pride and ego in the way then I'll just sit back and watch you all flounder around and develop even more false pride in "what you know" about these controllers. Again.. I'm trying to be patient with some here(you mostly) and will take some time to help you along as best I can but constantly revisiting things that have already been explained will surely just dry up my unthusiasm to do so. Sounds harsh and ultimatum like, I know.. but again with the "from the hip" attitude.

#4 I did say that early on but have since many times reworded that to say that there is surely soem other underlying issue at play. Over at OCZ forums I did acyually invite you to PM me as it's against the "forum recommendation" grain for me to recommend the way to do proper degradation/recovery tests on first gen Sandforce drives. I've helped many in PM environments and that should/has gone a ways towards letting those involved realize it's not about strutting around to act the "know it all" that some think I am. If I know it to be fact with quatifiable data?.. I'll tell you or even link it. If not?.. I'll clearly speculate and give detailed reasoning based on logic or past members/users experiences. I do know for fact that SE's can and often do go wrong with the ability to replicate failures at will. I now doubt that's the issue at play here.

#5 This is where the picture gets muddled and lost in translation. I see some clear issues with your perception of the throttled states starting to form as linked/discussed here in post #14.
http://www.ocztechnologyforum.com/fo...etime-Throttle

So, if the speeds were throttled immediately following an SE?.. there are a few possibilities from least likely to most.
1. The SE command did not initiate the drives internal ATA secure erase protocol. Seems unlikely at this point.

2. The drive has some form of firmware corruption or is just plain damaged. Also seems unlikely as these controllers don't just slow down and will panic lock quite easily if something is not right along those lines.

3. The testing methods to determine these states of throttle is flawed. Not sure if you were only relying on the AS SSD benchmark or if using Anvil's app? IOW, I need more clarification as to how you measured those speeds and after what amount of data written.

As for the "speeds being restored by an hour of if=dle time"? Well that right there will tell anyone that's familiar with a degraded Sandforce drive that there is ABSOLUTELY no way that a drive would recover from a degraded state in such a short timeframe. I've done oodles of degradation/recovery tests and seen more than my fair share of posters with speed issues over at OCZ forums and everywhere else for that matter, and none are able to invoke recovery in such a short timeframe. This controller is simply not aggressive enough to allow much moe than just a short little burst until the little fresh block recovery has been quickly spent again. And if the drive were actually in a "hammered state throttle"?.. there is NO, ZERO, ZIP, NADA.. chance that it would release any throttle whatsoever. The controller is actually coded to NOT release it that quickly and any form of recovery would definately mean that you were NOT in that state.

A lot to absorb and I can come off as a , I realize. But if you're seriously into learning and possibly fixing.. or at least modifying the testing parameters to achieve the desired result in the nedurance test?.. I may have some idea's to get you back into the running with this drive. Let me know.