Show all posts by user
4 years ago, by A2Razor in RAM Disk Forum
That's a fair point on that the allotment of memory between nodes (physically installed RAM) may not be equal pending the user's configuration. They might have 64GB on one node, and 32GB on the other (a total of 96 in the system instead of 128). Hadn't given occupancy much thought either, since I was considering spinning up a disk before launching other software whenever everything is relatively f
4 years ago, by A2Razor in RAM Disk Forum
Side note: my assertion that I could automate this using ramdiskc might've been a bit too hasty. I notice in the software help (user-manual, website, printed output of ramdiskc) that there's no option for specifying a NUMA node via cmdline (at least that I can see). RAM Disk Console 4.0.8 Syntax: ramdiskc /add:driveletter /param:value,... ramdiskc /del:driveletter /param:value,... O
4 years ago, by A2Razor in RAM Disk Forum
Not quite, I'm looking for a way to do cross-node controlled allocation (equal-split) rather than allowing the OS control over where the allocation takes place. Or rather, to allow for an allocation greater than the memory capacity of a single-node, without filling the memory of any given node. E.g, for a two memory controller system: half from node 1, half from node 2. Three: 1/3rd from node
4 years ago, by A2Razor in RAM Disk Forum
Just read through the whole "Software-RAID" idea built of RAMDISKS ... This is actually brilliant, peaked my interest to play around with, and will be leading into seconding the OP's suggestion of having this as an official feature. Specifically in the case of machines with multiple NUMA nodes without registered DIMMs, as a way to exceed the memory of a single-node in a disk without full