Scott, I realize you are a NAND guy, but can you pass along something to a colleague who might work with CPUs?Hey all,
Scott here from Intel corporation. I work for the NAND solutions group.
...
Let me know if you guys have any questions.
Even worse than that, he was a Lit major!Scott, I realize you are a NAND guy...
I think its more like there are technical challenges passing the required TRIM commands in RAID mode, like with SMART packets.You guys are over-analyzing this. Scott was just trying to say that the missing RAID support in Intel firmware isn't due to negligence i.e. Intel guys weren't idiots that overlooked it. Minimal returns on such an investment might have been the crucial factor.
Quote:
The idea is to allow more spare area for the drive's use in hopes that it will replace the TRIM function and allow read/write speeds to remain high.
In my case this has not worked and my read speeds have decreased by 50% in 6-7 weeks.
you got your answer through the other thread..
/post
maybe my english is bad, still i don't get you,There was?
I guess I shoulda asked you.
you got your answer, i was working few hours in order to figure out what happens there, and it even isn't written within anand's review, so instead of appreciating it, you just keep on with your line of childish behavior, and you DID ask others before this, and you DID got your question answered, so why asking it all over again?
No I don't but to me the question of "when are we getting TRIM in RAID" asked by 3 different people is a time waster. I'm sure Intel is aware and it's been asked a zillion times and asking a zillion more isn't going to make it any faster.do you like people wasting your time?
why would you waste others?
your read performance has decreased from 499MBps to 493MBps sequential, and another 3MBps per 4KB @ 64 thread..My statement about read times slowing was part of the background for the question about increasing the drive's spare area
In my case this has not worked and my read speeds have decreased by 50% in 6-7 weeks.
i never have asked this, that was sub.mesa, and your question as well was actually referring TRIM with RAID, that would be your ultimate solution.No I don't but to me the question of "when are we getting TRIM in RAID" asked by 3 different people is a time waster. I'm sure Intel is aware and it's been asked a zillion times and asking a zillion more isn't going to make it any faster.
You're correct it was the write performance that dropped 50% and I consider that more than nothing.your read performance has decreased from 499MBps to 493MBps sequential, and another 3MBps per 4KB @ 64 thread..
yeah, that's exactly the issue, when each is thinking whatever he like and nothing comes out of it.You're more than welcome to think what you want and I will do the same.
yeah, that's exactly the issue, when each is thinking whatever he like and nothing comes out of it.
the purpose of arguing, studying, asking and answering IS to find what is true, what is real, and what is not,
to clear out any doubts, to reach a level of new understanding,
so there's nothing like, you think what you like and i think what i like,
there's nothing like thinking what you like, there is only what is real, true, there.
and that is the point which was important here at this 'discussion', this is exactly what takes one to go on without paying attention to what has been said,
i think this is also a typical egoistic behavior where each is at his own planet.
and actually, have never brought this thread into any "silly" quarrels, there are things which are important to be said and notice, other wise you just spin around yourself endlessly, or till you figure your are spinning which is the first step out.
son't make it look petty and unnecessary,
it isn't,
other wise, i wouldn't have spend the time clarifying all of it.
I'm trying but at 58 I'm afraid it's a lost cause.grow up.
Alright. First of all thank you for dropping in these forums.I'm here to answer technical questions and make sure you guys are aware of the technical topics we're blogging about.
Alright. First of all thank you for dropping in these forums.
Let me ask you this: you're probably aware that performance on SSDs can scale very well because it's capable of doing true parallel I/O, as opposed to HDDs which are fundamentally serial based since they can only do I/O at one location at a time. Even with multiple heads the actuator still is locked to one position; thus HDDs are serial operation devices by nature.
Now the real question: what difficulties do you encounter when trying to scale performance? Couldn't you just release a 256-channel controller for example and push speeds into 1GB/s+ range? As long as you can predict the I/O pattern (sequential pattern; backwards or forwards of logical LBA), you should not have issues with insufficient queue depth. Upon two contiguous I/O requests you could assume the pattern is sequential and thus apply internal read-ahead to make sure all channels are busy.
So in my mind, i cannot see the reason Intel isn't pushing speeds against the interface limits. The Intel controller with SRAM cache (i believe 256KiB?) in X25-M does a very impressive job at latency and i still think its the best controller around these days even though SandForce and Micron are serious rivals when looking at both sequential and IOps performance.
Would Intel be looking more at PCI-express as interface instead? Why doesn't Intel build a platform on PCI-express where Intel delivers the PCI-express card with Intel native PCI-e to NAND-controller to the customer, and the customer can insert NAND to the PCIe controller much like SO-DIMM. So you could start with 2x 64GiB NAND and the controller will be able to do I/O faster when you add more NAND modules to the PCIe card.
If someone is capable of building such a platform, it would be Intel. High-performance storage would always be in demand, and Intel already has a head-start as it can build good native controller chips of its own.
Last question: ever considered integrating HPA mapping tables stored in DRAM memory chip to on-die SRAM in the controller-chip itself? Howmuch space would be needed and how big would the impact be on random I/O workloads?
That's all i can think of right now.
Thanks for your time! I highly appreciate and commend your efforts of posting on these forums.
you should get stronger inside,I'm trying but at 58 I'm afraid it's a lost cause.
Maybe you'll do better at it
your links have been deleted by the mods, you might want to add one at your signature so people can follow, same as JF-AMD does.This is the kind of stuff I came here to answer (not that I can and will answer everything in your post). I'll work on a response to this next week when I'm back at work, although I'll be at the Flash Memory Summit in Santa Clara for most of the week.
You guys are over-analyzing this. Scott was just trying to say that the missing RAID support in Intel firmware isn't due to negligence i.e. Intel guys weren't idiots that overlooked it. Minimal returns on such an investment might have been the crucial factor.
Scott, I'd like to know why Intel is not focusing on PCIe solutions. These are set to be game changers in the server space.
FusionIO cards deliver high-end SAN performance. When you're using a SAN for performance reasons, or resorting to large spindle counts in your DAS RAID arrays, these PCIe drives are far and away the better choice. I'm pushing hard at work to adopt this as our strategy instead of trying to build up a SAN infrastructure (which we don't have currently). We have multiple 100+GB databases running in multiple environments. Getting the company to agree to very large DAS arrays or a SAN has been a hard sell. So our DB servers continue to be the bottleneck. These PCIe drives will revolutionize the performance of our applications. I have just about gained approval for a server with 2x Z-Drive R2 drives to vet the tech and provide hard numbers to make the larger decision of whether to adopt this strategy across the board.How well does contemporary software support PCIe hotplug?
I thought the prevailing strategy in 'servers' was to move away from embedded storage altogether?
The miniPCI-E solutions with 40gb or 80gb should be very interesting as that's enough to get a server running with VMware or another virtualization solution, to boot VMs off a SAN.
Personally I'm surprised miniPCI-E is basically only seen in laptops right now. There's tons of applications, ranging from set-top boxes, home theatre PCs, and even desktops, that could make good use, instead of buying a clunky adapter card.
Because he has chosen to spend his free time to educate other users or at least answer their questions, when he could have just spent that time on his family. Instead, he has chosen to help 'us' by answering any questions we may have.i can't seem to over look the arrogance here,
why people are saying "thanks" to this guy for joining into the forum?
Competitors like OCZ are still selling SSDs without support for NCQ/AHCI, using the JMicron controller. The G1 has long been succeeded by the G2, which will get succeeded soon by G3. The G1 also never was advertised to have TRIM support either now or in the future. So i don't understand your hostility towards Intel for releasing the first generation of SSDs, which did not yet support TRIM. I also believe Intel was the first to release TRIM-capable firmware and adjust their drivers to support TRIM (not in RAID; no).i feel it is, they do all this crappy stuff with the G1's
Scott Dwyer graduated from the University of Illinois with a degree in literature. He works in Intel’s NAND Solutions Group, doing events and strategic social media marketing.
i think Intel did/is doing some inappropriate things, stuff they should openly speak about,I'm no moderator, but can i just ask politely to stop complaining to him about stuff Intel did wrong in your eyes?
Good, perhaps you are able to answer a question of mine!
We know Intel sells nice SSDs, and Intel knows TRIM is a hot feature here. Intel also knows people buy multiple SSDs and hook them up with RAID. We also know that TRIM does not work on Intel's RAID drivers with the SSDs being part of an array.
This i do not understand. If i were an Intel manager, i would have released TRIM-capable driver package - including full TRIM-on-RAID support - together with the release of TRIM-capable firmware. This way, Intel could benefit alot from increased sales of its SSD products since running them in a RAID does not cause the loss of TRIM capability on the array.
Considering TRIM-on-RAID works on other OS like Linux and FreeBSD (still limited support; granted) and the relative simplicity of passing TRIM (only need to take special care for split/combined I/O), i cannot understand why Intel waits so long with this highly anticipated feature in Intel RAID drivers.
Could you shed some light on this?
