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

Low Batch Requests/Sec? Expand / Collapse
Author
Message
Posted Tuesday, June 21, 2011 2:31 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, August 4, 2014 6:51 AM
Points: 244, Visits: 543
Hi All

System Info...
Server. 12G RAM, 2xQuad Core processors. Hard Drive C (RAID 1), Hard Drive E (RAID 10). 1G NIC
SQL Server 2008 R2. All system DBs on Drive C. 1 User DB, with Log file on Drive C and Data file on Drive E.

The application is Dynamics AX 2009 ;)

I have a report which is taking > 30mins to execute! I started the Activity Monitor and notices that the batch request/sec was about 1500-2000! with low CPU utilisation. Looking at task manager, the Network adapter (1Gb) was being utilised ~3%.

For who is not familiar with AX, the report is prossed on the AOS server (another server) and this server talks with the DB server. A lot of SQL statements are executed on the DB server and the results sent back to the AOS server which eventually will send the report back to the client.

I started suspecting the the DB server is not being fully utilised due to the low CPU utilisation and since the batch request/sec is low, it's not being hit hard enough by the AOS server. For a Gbit NIC, what network utilisation should I expect? Is there any guideline?

Regards
Brian


Regards
Brian Ellul
----------------------------------------------------------------------------------
Computers are incredibly fast, accurate, and stupid. Human beings are incredibly slow, inaccurate, and brilliant. Together they are powerful beyond imagination.
- Albert Einstein -
Post #1128824
Posted Tuesday, June 21, 2011 3:53 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Today @ 1:32 AM
Points: 83, Visits: 515
Have you looked at disk queue or memory paging?


Post #1128854
Posted Thursday, May 2, 2013 2:48 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, May 24, 2013 11:13 AM
Points: 3, Visits: 23
I have SQL server 2008 running on a Dell Server with 8 processors and 24 Gb RAM. Every few weeks the third party applications receives an SQL timeout issues which freezes other users. I then have to restart the server to bring it back on line. I have been running PerfMon and notice that my batch requests/sec were on average less than 10. My database is only 160 Mg and at most 25-30 user connections. Processor usage is minimal. Page life expetancy is over 300. Page splits are at time double the batch request/sec. Other performance parameters seem ok. Network connection readings are good. I set the memory max of 20 Gb and concurrent connections to 100.

Why would the system timeout? Could this be an issue regarding the programmin?
Post #1448982
Posted Thursday, May 2, 2013 3:14 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 4:17 PM
Points: 477, Visits: 1,047
rsorrentino (5/2/2013)
I have SQL server 2008 running on a Dell Server with 8 processors and 24 Gb RAM. Every few weeks the third party applications receives an SQL timeout issues which freezes other users. I then have to restart the server to bring it back on line. I have been running PerfMon and notice that my batch requests/sec were on average less than 10. My database is only 160 Mg and at most 25-30 user connections. Processor usage is minimal. Page life expetancy is over 300. Page splits are at time double the batch request/sec. Other performance parameters seem ok. Network connection readings are good. I set the memory max of 20 Gb and concurrent connections to 100.

Why would the system timeout? Could this be an issue regarding the programmin?



Why do you need to configure concurrent connection setting to 100. ??

By default it will be 0 and better to leave as it is as SQL server will allow up to 32000 and more connections.



--SQLFRNDZ
Post #1448990
Posted Friday, May 3, 2013 7:35 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, May 24, 2013 11:13 AM
Points: 3, Visits: 23
THe most user connecting to the server would be less than 100. I understood the limitation of changing it. My dilemma is having to restart the server every few weeks and I have been checking all the readings in perfmon. I can't tell if the server is the issue or the programming?
Post #1449195
Posted Monday, May 13, 2013 7:30 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, May 24, 2013 11:13 AM
Points: 3, Visits: 23
Like i stated, the batch requests / sec is very low. Less than 10. I have checked all network, memory, and cpu readings and they appear to be ok. What else could be a server issue before I go to my programmer to rewrite some of his applications?
Post #1452094
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse