Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

what performance metrics to show before and after optimization/tuning - to show improvement Expand / Collapse
Author
Message
Posted Thursday, January 2, 2014 1:58 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, April 28, 2014 10:18 AM
Points: 39, Visits: 91
question: If I am optimizing performance of a few dozen of SPs that i identified via Profiler Trace as taking most time while being the ones most often executed,
and did certain things to improve performance for particularly those SPs. Created some indexes, modified some TSQL inside those SPS, etc.
Now, after I roll out those changes to Production, i will need to show that my improvements/optimization actually has done something, and the performance/metrics are now improved.
Is the best way to prove that changes brought about positive results is to also run Profiler Trace and note that the same SPs ave(duration) and READS have become smaller values? Or is there something else that is useful to
show that modifications (mainly a few dozen of new indexes) have worked and performance is improved? I am thinking what would be most useful to include into my report to management that will show improvement after this tuning/optimization.
Thanks.



Voldemar
likes to play chess
Post #1527280
Posted Friday, January 3, 2014 3:50 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Today @ 6:32 AM
Points: 70, Visits: 463
You can test by mentioning SET STATISTICS ON/OFF while executing the SP.
Post #1527436
Posted Friday, January 3, 2014 10:24 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 7:48 AM
Points: 36,759, Visits: 31,214
Ravid_ds (1/3/2014)
You can test by mentioning SET STATISTICS ON/OFF while executing the SP.


Oh be careful now. SET STATISTICS is a known liar when it comes to certain forms of code. Please see the following article for proof of that.
http://www.sqlservercentral.com/articles/T-SQL/91724/


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1527780
Posted Friday, January 3, 2014 10:33 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 7:48 AM
Points: 36,759, Visits: 31,214
VoldemarG (1/2/2014)
question: If I am optimizing performance of a few dozen of SPs that i identified via Profiler Trace as taking most time while being the ones most often executed,
and did certain things to improve performance for particularly those SPs. Created some indexes, modified some TSQL inside those SPS, etc.
Now, after I roll out those changes to Production, i will need to show that my improvements/optimization actually has done something, and the performance/metrics are now improved.
Is the best way to prove that changes brought about positive results is to also run Profiler Trace and note that the same SPs ave(duration) and READS have become smaller values? Or is there something else that is useful to
show that modifications (mainly a few dozen of new indexes) have worked and performance is improved? I am thinking what would be most useful to include into my report to management that will show improvement after this tuning/optimization.
Thanks.


You need to show both because the indexes and other changes you make may have an impact on other things. Here's a URL to help you establish a baseline and then check and see what happens after the changes.
http://www.sqlservercentral.com/articles/baselines/94656/


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1527782
Posted Monday, January 6, 2014 1:45 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, April 28, 2014 10:18 AM
Points: 39, Visits: 91
Thank you Jeff.
Great article on base-lining that you have referred to. http://www.sqlservercentral.com/articles/baselines/94656/
1) So ideally base-lining would be an ongoing (daily) process with a job setup
that will write a snapshot of config + performance data to base-line tables?
2) and how about the query/SP performance data? The one that comes from DMVs. It does not appear too useful to store a snapshot of such info as the one from sys.dm_exec_query_stats or sys.dm_exec_procedure_stats on a daily basis because the metrics returned by this view get reset when Server restarts and SP is recompiled, etc. ? In other words, my main question is is what's the best way (in addition to Profiler Trace data) to also include an ongoing query performance info into the kind of recurring base-line data collection like the one referred to in the above article?



Voldemar
likes to play chess
Post #1528244
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse