In article <c6ccba43-0cda-499f-8055-bac996cd2458
@e6g2000prf.googlegroups.com>, email@example.com says...
You need to consider your other PROBLEM's and not just CPU.
SQL - needs one array for Data, one array for Transaction logs
O/S - should be on its own array
Files - should be on their own array
With a Quad Core CPU (Active Caching), your bigged hit will be the weak
Disk setup you have listed.
I have a very nice Dual CPU, Quad Core server with 4GB RAM, 12 Disks,
setup as I describe above, supporting 150 users that hammer the
We have a third party SQL server that only provides WEB/SQL data
connections that is screwed because the third party built the entire
thing on a single array, and everything is fragmented badly - 50K
fragments for the database files alone.....
You also need to understand how your applications (transactions) are
written when you are 8 cores for them to use - you will end up with more
blocking until the transactions are written with that in mind.
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
firstname.lastname@example.org (remove 999 for proper email address)