Yeah, RAM and CPU are mostly meaningless for a switch, it's just for management purposes. The big question is if the switch chip is stable or if it has problems like the other CRS models.
I support a CRS312 that has 64 MB with L3 HW Offload. The switch reboots every 2 weeks when Memory gets maxed out.
So for me CRS312, CRS5xx series and this new one is Dead on Arrival (Aside of the 3X times price issue for additional port speeds (2.5 Gbps) and couple extra SFP+ and 2 x 40 Gbps that the Industry is abandoning.
So there's two things here.
On the CRS312, I can say that I've had one running for well over a year and the only reboots it's had are for ROS updates. It's only doing layer2 and "the snoopings"; routing is disabled and it's only "reachable" via a management VLAN.
I "feel like" there's a memory leak causing your reboots, but it's definitely not in any of the modules/features that I'm actually using. Throwing more RAM at a memory leak is an expensive bandaid... My recommendation would be to monitor RAM use and once you see it getting "rather high", generate a supout and put in a ticket with it so that their boffins can have a look.
The second thing, I definitely have mixed feelings on the switching/ports.
40Gbe ethernet is the same generation of tech that 10Gbe is... so for shops and use cases that are still "fat, dumb, and happy" with the 10Gbe, then 40Gbe is usually still ideal... because at the end of the day, those 40Gbe uplinks can be broken out to separate 10Gbe connections if more ports are needed, and on top of that (in this specific case) a single one of those 40Gbe uplinks is likely to be enough to keep the bulk of the 2.5Gbe connections happy.
Using a newer asic that has native 25/100Gbe switching, instead of 10/40Gbe switching, would have made this CRS326-4C+20G+2Q+RM even more expensive.