• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1346
  • Last Modified:

CPU Speed or Cores for Terminal Server

I am building a new server to host Windows Server 2012 Terminal Server in Hyper-V sessions.  This will be an IBM x3550 with two CPUs.

We plan to host about 50 total users in two seperate VMs.

For the same amount of money, I can get 8 core CPUs with 20 MB cache running at 2.1 GHz or I can get 4 core CPUs with 10 MB cache running at 3.3 Ghz.

What is more important for terminal server, cores or speed?
0
richn
Asked:
richn
  • 2
  • 2
2 Solutions
 
Haresh NikumbhSr. Tech leadCommented:
0
 
richnAuthor Commented:
That test was for VDIs.  Do we know is the same holds true for traditional terminal services sessions?
0
 
Handy HolderSaggar maker's bottom knockerCommented:
With anything that involves a large number of threads such as terminal server cores always win over clock speed because each thread (and therefore each core) spends a lot of its time waiting on I/O. For the same reason you should enable hyperthreading so it can push the thread that's waiting on I/O to one side and run another thread on that core instead.

http://globalsp.ts.fujitsu.com/dmsp/Publications/public/Terminal_Server_Sizing_Guide_EN.pdf
Page 16(46) shows little difference (about 10%) between 2.0 and 3.16GHz but page 20(46) shows good scaling (70%) when doubling the number of cores.
0
 
Haresh NikumbhSr. Tech leadCommented:
correct that test was done for vdi. .if its such performance for vdi then ofcourse you get better on physical
0
 
richnAuthor Commented:
Thanks for the quick answers.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now