28. Response Time vs Workload Growth (reduced core, 3-node configurations)
29. Response Time vs Workload Growth (reduced core, 4-node configurations)
30. Optimized Configurations Final choice based on cost and management issues. Platform 3-node 4-node Sun SPARC Enterprise M8000 (2.4 GHz) 32 24 HP rx8640 (1.6 GHz, 25MB L3 cache) 30 24 IBM p 570 (2.2 GHz, Power 5) 26 20 IBM p 570 (4.7 GHz, Power 6) 12 10
31. June 21, 2009 Performance Analysis SQL Server on HP Blades and EVA
32.
33.
34.
35.
36. June 21, 2009 Not really high IO counts these days…. IO Rates
37. June 21, 2009 Very high D: drive response time…. Disk Response Time
38. June 21, 2009 Very high D: drive response time…. IO Sizes
39. June 21, 2009 SQL Server process generating all the IO Obviously, something wrong with the application, right? Process-based IO Rates
40. June 21, 2009 1.7Gb. Excuse me? But the server has 24Gb of memory SQL Server Memory
41. June 21, 2009 Soft paging into the free list SQL Server paging
42. June 21, 2009 Soft paging into the free list huge IO load generated as data I s moved to and from the SQL Server process SQL Server paging
49. June 21, 2009 : Production: Disk Busy Q after HUGE reduction in disk busy
50.
51.
52.
53.
Notas del editor
Note that having experience of the other side of the fence – (almost adverserial) Compaq/DEC background.
Server numbers peaked 2005-2007 Windows/Blades/Virtualiasation All platforms (worse with Solaris x86) Not seen as a value add
CP and Performmance Specialists are almost extinct Replaced by ITIL Capacity Management Specialists – not the same thing! CP 99% of cases only under infrastructure budgets – not aligned to business Experiences with ITIL found – good for developing processes, bad for developing budget Suits management not to have overall department with responsbility for Infrastructure and Applications
CP and Performmance Specialists are almost extinct Replaced by ITIL Capacity Management Specialists – not the same thing! CP 99% of cases only under infrastructure budgets – not aligned to business Experiences with ITIL found – good for developing processes, bad for developing budget Suits management not to have overall department with responsbility for Infrastructure and Applications
This was for a 4 way Sybase Server which today could be performed by a single blade server on the end of a SAN Point here: with a server costing so much you NEED to make sure that it is correctly sized – today better performance for less than ¼ fo the price – is that why many sites have 4x the servers?
This was for a 4 way Sybase Server which today could be performed by a single blade server on the end of a SAN Point here: with a server costing so much you NEED to make sure that it is correctly sized – today better performance for less than ¼ fo the price – is that why many sites have 4x the servers?
Clearly, something odd is happening here
Clearly, something odd is happening here
Server was a BL460c 4Gb FC cards, 24Gb of memory
Asked the question: what was the EVA configuration: EVA6000, 300Gb 15k drives, 96 disks. Shared Modelled EVA to confirm issues….
Ah, first clue, large sizes of IO 80,000kB/sec = 8000MB size, 8Gb xfers !!!!!
All SQL Server, mostly during on-line day.
SQL Server has 1.7Gb, is enterprise edition, and SLQ server memory has been set to use all the memory it can.
So, what happens when SQL cannot get enough memory – it will soft fault…
So, what happens when SQL cannot get enough memory – it will soft fault…
ALL SQL servers had this issue. Looks like the customer forgot to implement the feature…. But what happened next?
So, what happens when SQL cannot get enough memory – it will soft fault…
So, what happens when SQL cannot get enough memory – it will soft fault…
So, what happens when SQL cannot get enough memory – it will soft fault…
So, what happens when SQL cannot get enough memory – it will soft fault…
We put the change on a stress test system
We put the change on a stress test system
Since this work, the fix went in onto another SQL Server – Disk read queue of 34m peak down to 300. Analysis was’t hard to do, just no-one had done it before.
ALL SQL servers had this issue. But what happened next?
To start with, just getting decent performance data was a problem Then came the issue of logging into each system and looking at the graphs Then came the issue of looking at 100s of systems Then came the issue of modelling