July 11, 2016 at 1:50 am
Hi Experts,
The BatchRequest\Sec value for our OLTP system is showing 150 for the most critical time. I felt this as very low , can you guide me on what else i need to check to make sure everything is running smooth for system.
July 11, 2016 at 2:00 am
VastSQL (7/11/2016)
Hi Experts,The BatchRequest\Sec value for our OLTP system is showing 150 for the most critical time. I felt this as very low , can you guide me on what else i need to check to make sure everything is running smooth for system.
Quick thought, that's roughly 500.000 in an hour, not that quiet as each batch can and will entail one or more executions.
😎
July 11, 2016 at 2:11 am
you felt that it was low compared to your baseline?
July 11, 2016 at 2:47 am
Eirikur Eiriksson (7/11/2016)
VastSQL (7/11/2016)
Hi Experts,The BatchRequest\Sec value for our OLTP system is showing 150 for the most critical time. I felt this as very low , can you guide me on what else i need to check to make sure everything is running smooth for system.
Quick thought, that's roughly 500.000 in an hour, not that quiet as each batch can and will entail one or more executions.
😎
Thanks for the response. You mean to say this is a good average?
July 11, 2016 at 2:47 am
BLOB_EATER (7/11/2016)
you felt that it was low compared to your baseline?
Trying to create a baseline and this is the highest i got.
July 11, 2016 at 3:07 am
VastSQL (7/11/2016)
Eirikur Eiriksson (7/11/2016)
VastSQL (7/11/2016)
Hi Experts,The BatchRequest\Sec value for our OLTP system is showing 150 for the most critical time. I felt this as very low , can you guide me on what else i need to check to make sure everything is running smooth for system.
Quick thought, that's roughly 500.000 in an hour, not that quiet as each batch can and will entail one or more executions.
😎
Thanks for the response. You mean to say this is a good average?
In my experience that is quite good for a small/medium sized server, guess that the transaction rate would be close to 500/sec and the execution rate around 3-4M/hour.
😎
July 11, 2016 at 5:45 am
How are your wait statistics?
This indicator is just an indicator of load. If it goes up or down compared to the baseline (which I get that you're just establishing), it has meaning. However, the number, in isolation, has no particular meaning. Is 200 better than 150? Who knows? Put that in combination with wait statistics and queues, comparing it over time to those over time, then toss in blocking & deadlocks (if any), and you'll start to understand what's happening on your server and whether or not it's problematic.
Don't get hung on a single indicator as being important. It's just as bad as when people get all wrung out over Page Life Expectancy. Same thing. The number is only meaningful when compared to the baseline and when compared to other numbers. By itself, it's useless. Same thing here. Same thing with a lot of the performance counters.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2016 at 6:18 am
Grant Fritchey (7/11/2016)
How are your wait statistics?This indicator is just an indicator of load. If it goes up or down compared to the baseline (which I get that you're just establishing), it has meaning. However, the number, in isolation, has no particular meaning. Is 200 better than 150? Who knows? Put that in combination with wait statistics and queues, comparing it over time to those over time, then toss in blocking & deadlocks (if any), and you'll start to understand what's happening on your server and whether or not it's problematic.
Don't get hung on a single indicator as being important. It's just as bad as when people get all wrung out over Page Life Expectancy. Same thing. The number is only meaningful when compared to the baseline and when compared to other numbers. By itself, it's useless. Same thing here. Same thing with a lot of the performance counters.
Thanks Grant.
I started logging BatchRequest\Sec to understand the load on server, can you help me add more counters to list?
July 11, 2016 at 6:31 am
VastSQL (7/11/2016)
Grant Fritchey (7/11/2016)
How are your wait statistics?This indicator is just an indicator of load. If it goes up or down compared to the baseline (which I get that you're just establishing), it has meaning. However, the number, in isolation, has no particular meaning. Is 200 better than 150? Who knows? Put that in combination with wait statistics and queues, comparing it over time to those over time, then toss in blocking & deadlocks (if any), and you'll start to understand what's happening on your server and whether or not it's problematic.
Don't get hung on a single indicator as being important. It's just as bad as when people get all wrung out over Page Life Expectancy. Same thing. The number is only meaningful when compared to the baseline and when compared to other numbers. By itself, it's useless. Same thing here. Same thing with a lot of the performance counters.
Thanks Grant.
I started logging BatchRequest\Sec to understand the load on server, can you help me add more counters to list?
Chapter 5 of my query tuning book has a complete listing. Chapters 2-4 give you all the detail behind the listing, what each counter is, why it's interesting, and what other material you might want to compare it to in order to arrive at additional meaning. There are also listings of the various different tools, mechanisms, etc., needed to set up monitoring on your servers. It's all there.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply