So just out of curiosity what apps are you running that generate this kind of I/O?
Would not a few SSD's in a RAID 0+1 configuration, or even just striped handle your I/O requirements?
With a server board you are going to have to get ECC memory which is good stuff. I wouldn't build a proper server without it.
That being said check this out:http://www.tomshardware.com/news/ocz-z- ... ,8589.html
PCI-E SSD drive with capacities up to 1TB and I/O of 768MB/s.
Sure it'll be expensive as heck, but so will a server board and 144GB of ECC DDR3 memory and quad core Xeon Processors.
I think you would get better I/O from the PCI-E bus and SSD solution than you would from a traditional RAM drive. I'd build a Quad core i7 or dual proc quad core i7 machine with 32GB of RAM an SSD boot drive, a RAID 5 array for storage and the PCI-E SSD card for your temp I/O and transfer needs.
Just a thought.
Hey, thanks for the ideas here...that's a pretty nifty drive you referenced
* All of the I/O is write only, which is why I hadn't considered conventional or SSD type drives. If it were read, then an SSD would be the way to go.
* Ramdrives are so much faster than anything I've encountered(for writes). But, they are very expensive, and do suck up some cpu power to manage.
* Currently, I'm banging my drive ~1 sec intervals. Would like to ratchet that down to at least .5 sec, and preferably lower, while increasing the amount of I/O data by at least 3-4 times. So, you can see why I leaned towards ramdrive + high horsepower chips.
* Best I've found for pcs is 32G(maybe 48G?) of ram, which ain't enough. Therefore, off to server land. If anyone knows of a tower type pc setup that'll hold more memory, lemme know. Interestingly, Win7 maxes out at 192G, but the Xeon chips appear to max out at 144G(!) It might be possible to have the I/O go to a 30-ish Gig ramdrive, then have a background Win task offload that data periodically to a staging drive, but I'd rather not mess with that approach.
* SSD issues over time with extended write activity, so not sure I wanna go the SSD route, but will re-investigate. Currently, I'm writing ~14G data/day/prime time Mon-Fri, then compressing it later for archiving(14G-->300M; high compression). Short bursts of really quick write I/O, not sustained I/O activity. Cranking this up could well get me into >= 100G/day, and I'm not sure how long an SSD drive would hold up, and what kind of degradation would occur...could be, a really fast conventional drive + RAID would do the trick. That, with an i7 chip, maybe overclocked a bit, might just do the trick. Would be a lot cheaper, too
I don't need a super huge size drive, just sumpin' realllly quick. I might add that it would be within the budget to replace SSDs periodically, if necessary, but I'd like something that'd hold up for at least a few months. So, SSD is not out of the question(yet).
* I also have a problem with the apps, in that I have one app that generates the data, and another that does all of the write I/O activity. Each is uni-processor(crap), so even tho I don't need a bunch of cpu cores(etc), I do need cpus that are on the fast end. If I ended up going with the server route, most of the cpu would be unused, but there'd be a couple cores really spinning away.
Ironically, I exceeded my original plans using a W700 and some Matrox monitor line splitters. If a little bit is good, a LOT is GREAT; has me thinking about expanding...ha, ha.
In view of all of the above, spec'ing out a server setup is gonna cost a LOT of $$$(
), and if there's some possibility of a drive out there that'd work(Raid, too; hadn't really considered that), I'll take a look. And, last time I actually built my own box was back in the '90s; would rather buy sumpin' already assembled...
Any more ideas, keep 'em coming...