Sign in with
Sign up | Sign in
Your question

server cpu: Cores vs speed for databases

Tags:
  • Database
  • SQL Server
  • Speed
  • Business Computing
  • Servers
Last response: in Business Computing
Share
September 5, 2014 3:50:41 PM

Hi,
I'm trying to configure an updated server for our medical office. We have 4 databases for a total of 200 GB where speed is desirable, and 2 archival databases of 100 GB where it isn't. All are below sql server, with a sql server express, 3 MS Access, and 2 Advantage database programs.
I am getting adequate speed on a 5 year old server with a Xeon E5504 @ 2.0 GHz (4 processors) with 16 GB ram.
Rather than buy a bleeding edge server, I would rather buy 2 identical servers in the lower end to middle of the sweet spot for redundancy.
What would you recommend for the number of Xeon cores?
For similarly priced CPUs, is it better to have more Cores than needed at lower speed or higher speed with minimum cores?
How much RAM would allow getting less expensive CPUs for my multiple small databases?
Thanks, Dan

More about : server cpu cores speed databases

September 5, 2014 4:45:22 PM

How many simultaneous people (or applications) access your DB? If you have hundreds then more cores will probably improve performance. If it is a few, then fewer faster clock speed cores will help. There is NO SUBSTITUTE for RAM when it comes to databases. The more of the data that the DB can hold in RAM the better. Get a server (or motherboard) that can have ECC RAM and get 32GB or 64GB. Also with databases as small as yours, PCIe SSD is a distinct possibility. If not entirely on SSD there are accellerators that can improve things.
m
0
l
September 5, 2014 5:06:25 PM

Thanks kanewolf,
There are 20 of us with everyone interacting with one of the databases almost constantly during business hours, while almost everyone is keeping 3-4 databases open.
Thanks for the rec on RAM and SSDs!
Dan
m
0
l
Related resources
September 5, 2014 5:21:37 PM

There are LOTS of articles on SQL server tuning, take advantage of those also. If you were going to force me to pick a CPU, I would probably pick something like E5 v2 Xeon. Not too power hungry, dual socket compatible, hyperthreaded (your mileage may vary, so check it with hyperthreading on and off).

The HP DL380 gen 9 servers are set to be announced any day now. They should use the V3 Xeons.

The value of having somebody from HP (or Dell or IBM) to call when it goes south can't be over emphasized...
m
0
l
September 5, 2014 6:11:43 PM

Thanks kanewolf,
Thanks for your help, and I hear you on your last point. I will wait to see what happens to prices with the v3.
Dan
m
0
l
September 19, 2014 11:09:20 AM

I don't think the recommendation should just be about the hardware costs. You really need to be aware of licensing costs as often that can be more than the cost of the server hardware. For SQL Server, you're looking at per-core licensing or Server+CAL licensing, so be careful before you jump out & buy something like dual octal-core processors. That could prove to be very expensive if it really isn't required.

If you're a medical office, you likely run a software package with specific hardware & software requirements, so check them out first. In fact, talking to their tech support will give you a better idea of where to allocate your funds.

For databases, it's all a balancing act between memory, processor speed, disk I/O, and core count. Of all of them, core count is probably the lowest contributing factor because virtually all database-class Xeons are going to be quad-core at the minimum.

So if a 16GB, quad-core 2.0GHz Xeon is working for you now, perhaps the most cost-efficient and "noticeable" speed upgrade you can make is to get a quad-core 3.0-3.6Ghz quad-Xeon (like a E5-26xx v3) with an upgraded disk subsystem like an all-SSD RAID array. Keeping the same core count won't increase your licensing costs. Look at SSDs that are prioritize maximum long-term durability and speed. You may even considering rolling your own disk array, and choosing something like all-Samsung 845DC Pro array. A fast disk subsystem will let your processor chug through stored procedures and big reports much faster; that, in turn, saves time (and thus $) for every user accessing it.
m
0
l
!