• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Need a new DB Server

longblock454

longblock454

2[H]4U
Joined
Nov 28, 2004
Messages
2,880
Current server:

Xeon E5-2620 v4, 8-Core, 2.1G base 3.0 Turbo @ 85w TDP
Supermicro X10SRi-F
256G ECC
4 Spinners and a 10G network card
DC/Solar Powered via M4-ATX

This server is about 8 years old with a 10y old SSD, need to upgrade before it bites me. This is also a file server but most importantly a DB server for a large number of homebrew IoT devices and home automation. Current DB (mariaDB/Linux) size is about 100G/2B rows, growing fairly quickly averaging ~400qps, performance is becoming meh. Let's not talk about query optimization or old record warehousing etc.

Want I'm looking for is something about like:

AMD EPYC 4564P, 16-Core, Base 4.5G Max Boost 5.7, TDP 170w
Supermicro H13SAE-MF
Max for this system is 192G ECC, only 4 Dims though, this is available but I'm worried about compatibility with large sticks and I'd really like the ability to jump to 256 or perhaps even 512 in the ~8-10 year lifespan of this server.

This system will also be DC/Solar powered so TDP is important, also want to keep IPMI but I don't really see much in the way of options for more RAM without going all out. Also need suggestions on more robust NVMEs in the 4BT range.

Any suggestions i've missed?
 
longblock454 said:
'm worried about compatibility with large sticks and I'd really like the ability to jump to 256 or perhaps even 512 in the ~8-10 year lifespan of this server.
Click to expand...

If large memory is a requirement, using a desktop socket is going to be limiting. You really need to get on a server socket (or HEDT) to have lots of dimms, and then you get all the cost that comes with that.

I know you didn't want to talk query optimization, but if your database is smaller than RAM (which it seems likely, if you're not doing other RAM heavy stuff...) you shouldn't be stuck at 400 qps. Either your config is wrong, your queries/indexes suck, or you need more ram. If you need more ram, more faster cores won't help much when it comes with less memory. Although if you get NVMe storage vs SATA, that could compensate.
 
toast0 said:
using a desktop socket is going to be limiting
Click to expand...

Was hoping I missed something, the 4000 series EPYC stuff and their high clocks are unusual, sucks they are all suck on AM5.

toast0 said:
shouldn't be stuck at 400 qps
Click to expand...

I'm not stuck yet, it's currently running about 40% duty on the current hardware but i'm expanding the data collection and sophistication of the queries all the time.

I may hold off for EPYC 9005s and move to socket SP5. Will have to revamp the power delivery but perhaps unavoidable.
 
I'd keep the Xeon and give it new drives. RAM rocks and DDR4 registered is dirt cheap. 4 x 48 GB DDR5 UDIMM ECC costs a fortune.

You can also put a faster v4 CPU with more cores.
 
Decided on a direction change, pooled together 3 NUCs and have been learning Proxmox over the past couple months Instead of building a new all-in-one server I have put together a cluster of used gear and am quite happy playing around with high availability and everything else proxmox offers.

So far couldn't be happier with the change.
 
You must log in or register to reply here.
Back
Top