Acard ANS-9010B 5.25-inch SATA x1-to-6-slot DDR2 RAM Disk (Deactivated)
scsi4me.com
scsi4me.com
I'm not in anyway connected to this, found it after looking for something modern after seeing a YouTube video about old ramdisks.
Possibly scattered 1-byte writes rather than sequential 4096-byte page writes.
Looking at the memory price timeline https://jcmit.net/memoryprice.htm it was middle 2007 when 1GB memory hit $50 (row 2007.33 it's a very big drop in $/memory as you can see in the second column). A contemporary server motherboard would be the Supermicro X7DCL https://www.supermicro.com/manuals/motherboard/5100/MNL-0957... with six slots of DDR2 memory capable of handling 48GB RAM https://ark.intel.com/content/www/us/en/ark/products/33142/i... but even with cheap memory it was easily doing 12-24GB RAM.
Looking at it from another angle, https://github.com/memcached/memcached/wiki/ReleaseNotes150 "Memcached was introduced in 2003" which is a bit after Socket 604 and looking at those boards https://www.supermicro.com/products/motherboard/archive/?mlg... it does not seem like at that era 8GB maximum would be uncommon (8GB instead of 4GB because we want to use cheaper than top modules), in fact very few motherboards top out at 8GB, most could do a lot more. This is to say, there doesn't seem to be a period of history where memcached existed but commodity servers handling more than 8GB didn't exist.
Yet another angle, I upgraded from the Panasonic CF-Y5 to a ThinkPad T400s because the CF-Y5 topped out at 2GB and that was in 2009 (I checked my records, 2009 August 11) and so servers not handling vastly more is extremely unlikely. At this time the company I worked with certainly had dedicated memcached boxes yes, but a lot more than 4GB RAM, can't remember exactly how much.
I would cautiously say you misremember your numbers.
1) that was a premium motherboard, 2) 16 ram sticks were way more expensive per GB than smaller sticks. I think you have the timeframe about right (2008?), but where I worked we had 1000s of servers built on PC motherboards (cheap) with 4 slots holding 1GB each. 4GB sticks existed but cost a lot more per GB and were hard to find, and our motherboards needed some kind of bios change to use them. We did manage to upgrade a few machines to 16gb and they were useful.
Another reason could be size - in a 5.25" form factor, you could potentially "stack" several m2 SSDs in blade-like fashion. I haven't seen such a thing though, and heat might be an issue.
So there are 5.25” multiple m2 adapters out there like
https://www.icydock.com/goods.php?id=255
That one would require a sas controller to connect to.
You generally don’t see a tighter system like blades due to needing a bifurcated pcie slot support, which at that point of server hardware, your are generally not using adapters like this.
Is the ability to bifurcate a PCIe slot (and avoid extra controllers) that rare? That's a shame.
I have a https://www.supermicro.com/en/products/motherboard/X10DRH-iT and they don’t support bifurcated pcie. It’s a shame cause I’ve extended the life of the servers by using pcie adapters to add high speed io layers and I’m limited to one device per port. I’d love to double that density.
Hot swap bays are usually set up for 2.5" drives. You can fit 4-8 into a single 5.25" slot. But the ones designed for performance will prefer U.2 drives and hook them up to PCIe.
Gonna take quite a while for such raw versions to emerge. Gonna be stupid expensive enterprise drives for years. But really it could be just a chip with some ram controllers & a CXL port.
Alas the fpga market is a lumbering hulking ancient shit show. Lattice put out a solid mid range part but the whole rest of the market is dead, unless you want chips that cost as much as cars for milspec radars or whatnot, then there's great shit. What a hellhole, such a core base for computing, unserved.
So it's not even as fast as a modern SATA SSD. Oof.
Uses ddr2 and ram was expensive when it came out, so can see it wasn't super popular. But neat idea.
https://techreport.com/review/16255/acards-ans-9010-serial-a...
https://techreport.com/review/16255/acards-ans-9010-serial-a...
Say, most things you put in /var
This particular unit might also work for a machine where you install a client OS on the main (ramdisk) HD and reboot, then wipe and do it again later.
>Say, most things you put in /var
Even a bottom of the barrel QLC SSD can handle 100GB of writes per day without problems. Therefore it's unlikely that moving stuff in /var (random log/temporary files) off the SSD is going to change its lifespan by much.
That's enough to write a 100 Mbps high quality local copy of a 24/7 stream for the 6 years.
But resorting to a ramdisk means you have failed. most of the time the page cache offers the semantics you actually want, memory quick access backed up by persistent storage. You are saying, I want a filesystem api with ram speed and are willing to jump through the hoops required, manually syncing your storage at startup and shutdown, to reach that specification.
If you are thinking about a ram disk it is likely because you want guaranteed low latency. With a cache you get hosed by delays when pages are flushed. I remember having to run daemons just to keep caches warm by periodically accessing data that I might need later without having to wait for it.