SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Transaction/Sec on tempdb


Transaction/Sec on tempdb

Author
Message
NicHopper
NicHopper
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2452 Visits: 1908
Hi all,

I've been doing some server bench marking on one of our production SQL 2K5 instances, one thing I did notice was the transaction/sec counter (using performance monitor). So I did a little more digging around and found nearly all of the activity for this counter is on the tempdb.

My question is, I assume this is being caused by operations which are occuring in the tempdb such as sorts, orders, temp tables etc. Is this correct? and if so, is this operation worse (in general) than the transaction/sec being done in one of the user db's rather than tempdb?

I know this is a bit of an open ended question, there are no noticable performance issue with the server but i'm trying to be pro-active and anywhere I can increase performance would be a benefit.

Thanks in advance.

------------------------------------------------------------
Check out my blog

http://www.sqlservercentral.com/articles/Best+Practices/61537/
MANU-J.
MANU-J.
SSCertifiable
SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)

Group: General Forum Members
Points: 5054 Visits: 8766
Are you making selection out of the available databases listed on the right hand side when you click on Transactions/sec counter?

MJ
NicHopper
NicHopper
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2452 Visits: 1908
Hi,

Yes, original I just looked at the total, then to try and find the cause I added the user db's and the temp db.

As mentioned the tempdb accounts for approximately 95% of the total transaction/sec.

Thanks.

------------------------------------------------------------
Check out my blog

http://www.sqlservercentral.com/articles/Best+Practices/61537/
PaulB-TheOneAndOnly
PaulB-TheOneAndOnly
SSCrazy Eights
SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)

Group: General Forum Members
Points: 9627 Visits: 4639
tempdb utilization is a function of the application, in your case application was developed in a way where it does heavy use of features that end up hitting tempdb.

Question for you... is this intense utilization of tempdb creating an I/O bottleneck?

In the affirmative case. A way to improve performance in regards to tempdb is to spread it in as many datafiles -located in different disks - as processors you got in the server. The rationale behind this strategy is that SQL Server would manage work load across all these datafiles then minimizing the chances of seeing I/O bottleneck.

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search