Quote:
Originally Posted by
Computurd
I do not own l4d and dont intend to. I do not run games as benchmarks, too many variables. then you will complain about my tri-sli and overclock and ram speeds.
Running games/apps is the only way to really measure performance. You can run from it all you like, but I have a feeling you are already aware of how slow your PC is in comparison to others.
Quote:
that is why i run benchmarks, it does the most that can be done to alleviate the BS. One benchmark i do not use is as ssd as it is unreliable when benching hardware raid solutions. it works fine on normal ssd's but gives borked, random unreproducale results in tandem with hardware raid. that is a known problem with many benchmark programs that is why professionals, intel included, run i/i meter.
Yes, AS SSD doesn't work well with cache. Do not tell me about iometer. I have started getting people to use it about a year ago, back when hdtach was king. Then ATTO came around and I was still trying (failing) to get people to use iometer due to people like Tony (ignorant at that time) saying ATTO is a great measure simply because it showed overrated results and was quick and simple. Only very recently did people accept it. So please don't tell me about it.
Quote:
on the page 8 of that intel pdf it says nothing of 4k random access MBPS. it says about iops. not what you are saying it says. i looked at that very white paper before i posted above.
basic math fail... 35000 iops @ 4kb = 140,000 kb/s.
Quote:
on AS SSD i believe the 4k-64 means 64 queue depth, but i am not sure. that is not what i am speaking of. the 4k on my results is 150+ with crystal bench mark. there isnt a x-25 out there that can get close to that 4k throughput. I have posted every test imaginable to prove to you what i am saying.
Yes it means 64 queue depth. It does the same speed at 32 (in fact I dont think Intel SSD support/do anything past 32). Are you saying your iometer run showing 35k iops was with less queue? Your CM run is 100% cache. Take your own advice and use iometer.
Quote:
Now you are down to saying..."run a game you will see?"
surely you are joking.
Not joking at all. Your L4D will take 9++ seconds to load and you will see. It doesn't have to be l4d. You must game a lot if you have tri sli, so you have to have a lot of games.
Quote:
i believe that no matter what i post here, you will continue to say something else different. i have beat it at iops.; i have matched access/response times. i have matched it , or beat it at all throughputs. i am more than willing to run any i/o meter test that you wish to prove yourself correct. but you aren't. period.
You haven't posted anything but useless 8k runs that involve 20% writes. And in those useless 8k runs you get smoked by mere 2x x25-Es. Your access time is 0.23ms (looked at some of your benchmarks from before), which gets beat by 2x by almost any ssd. Your 4kb random iops is equal to a single x25-m (ioxtreme is a few times more than this). Max throughput is irrelevant.
Quote:
i could post a video of this raid card growing legs, walking on water, curing cancer, then creating world peace. you will come back with...that card is crap. i was thinking of taking my card off of this slot that has the nf200 and pulling my other two video cards, because that adds about .05 latency to my array, as the nf200 is a bastage. but what would be the point? i have beat the thing without even disabling services or turning off my gadgets on my desktop for the love of christ.
You haven't beat anything. And turning off services and such doesn't change iops by more than 1%.
Quote:
by the very logic you proclaim then the i/o extreme is a piece of crap as well. this lsi has beat the 1231 with ACARDS IN RAID 0 at iops. still a piece of crap! LOL
Perhaps at an irrelevant IOPS setting at an irrelevant queue.
Quote:
you have to also understand, that 4k is not the end all, or even the begin all, of storage solutions. you have such a narrow view of performance that it is laughable.
here is annandtechs results for different computer usage patterns:
The light trace is composed of 37,501 reads and 20,268 writes. Over 30% of the IOs are 4KB, 11% are 16KB, 22% are 32KB and approximately 13% are 64KB in size. Less than 30% of the operations are absolutely sequential in nature. Average queue depth is 6.09 IOs
heavy trace:The benchmark is 22 minutes long and it consists of 128,895 read operations and 72,411 write operations. Roughly 44% of all IOs were sequential. Approximately 30% of all accesses were 4KB in size, 12% were 16KB in size, 14% were 32KB and 20% were 64KB. Average queue depth was 3.59.
he gaming trace is made up of 75,206 read operations and only 4,592 write operations. Only 20% of the accesses are 4KB in size, nearly 40% are 64KB and 20% are 32KB. A whopping 69% of the IOs are sequential, meaning this is predominantly a sequential read benchmark. The average queue depth is 7.76 IOs.
I have posted this EXACT ARTICLE BEFORE IN THIS VERY THREAD. Read post #32. I do NOT think 4kb is the only measure; it is one of the relevant ones. Try to read before posting.
Quote:
now these are people who know what they are talking about. professional. note that the gaming trace, which is what you are purportedly using your system for, has the LOWEST MIX of 4k reads. interesting. ALSO the highest percentage of sequential IO's. and what is that queue depth of?? 7.76!! that is extremelly lower than the x-25 64 queue depth results you keep mentioning. so then would you say that this lsi would absolutely KILL that l4d loading time, eh?? 1.75 gb/s seq should just about do it.:rofl:
Funny. The 8k you keep running isn't even a part of the trace. And you are certainly not running queue of 8 with 1 worker like the article suggests. Try that out and see what happens. And that 8 is average. Meaning, it ranges with use from 1 to whatever the max is. Your 4kb bandwidth @ queue of 1 is like 17mbps (comparing to ioxtreme which is 40+).
Quote:
There has been much much discussion about what the computer really uses as it loads and uses an OS., what is the mix of reads/writes, inputs/outputs, randoms/sequentials? Over at OCZ they took a program, much like anandtech did, and monitored the usage of the operating system throughout all phases of use. from this they derived a I/O meter profile, it mirrors real usage, that you can download, that has a realistic mix of computer inputs/outputs. I would love for more people to run it, as it is real world test. the profile is called BOOTUP and they need to include it with downloads of I/O meter!!
you can get it here:
http://www.ocztechnologyforum.com/fo...05&postcount=2
i really wish more people would get their heads outta the sand on these things, as you can see from the articles at anandtech, and other very highly respected sites, real world usage actually entails a very small mix of random 4k file usage.
You can not mirror real world usage with iometer. It is impossible. The config they have made has absolutely no relation to the real world. It is just a read/write test with 4kb-64kb files @ queue 64. First of all the queue is all wrong as you have already mentioned.
Second of all (and more importantly) this approach is inherently wrong. Let me dumb it down for you so you can hopefully understand. Say you have a program that does 100% reads for 5 seconds and 100% writes for another 5 seconds. Tracing it and converting it to iometer would run this "real world simulation" as 10 seconds of 50% reads/50% writes, which would produce a result that is COMPLETELY UNRELATED to the performance of the original application. Running a very complicated simulation, like bootup just makes it even more useless if that is even possible.