Server Performance and Axapta...
-
All,
I am having issues with the performance of my servers while running reports in Axapta (Microsoft EPR tool). The users are complaining of slowness and the Server's CPU usage is going through the roof. We have a few choices here.
1.) First, the servers are 4-ways and we are looking into making them 8-ways so that the CPU's can better handle the workload.
2.) The second choice is to set up replication on another 8-way server and get the reports with the heaviest workload off of the Production box into a seperate reporting environment.
3.) Both of the above.
Has anyone had any experience with Axapta, and if so, what, if anything, did you do to resolve any performance issues that you may have encountered?
Thanks in advance,
Ben
-
This was removed by the editor as SPAM
-
1) Have you verified what is takin all the CPU cycles and have you checked the Event Viewer logs for any issues before you assume the slowdown is in the software or database? We had a previous issue where additional CPUs were introduced becuase they believed my software was the reason the server was sitting 100% of the time at 70% or better utilization. After they tried pointing the finger here and there I asked them to check Even Viewer and it turned out a piece of hardware was screaming failures into the log which was taking all the utilization we were seeing.
2) When was the last time you refreshed your stats and indexes by hand. Sometimes simple maintenance ca make a huge difference.
3) Hav you checked the worst queries t see if a index addition or chang might have a big impact.
4) I think a seperate reporting server is a great idea espeically if you hav a lot of ad-hoc or on demand stuff.
5) I haven't used Axapata but I do believe it supports timin reports for storage (could be wrong), if so look at reports ran one or twice a day and consider creating saved versions that referesh periodically. If you have 500 users hittin a report on demand once every morning an the data is fairly stale anyway then reducing it to one run and many pulls of the static version will save you a lot in the long run.
-
Thanks for the reply... We are still having issues with performance but I think that we've narrowed it down to bad data and/or equipment issues at this particular remote site. But, to answer your questions:
1.) CPU cycles = System Idle Process 86, sqlserver.exe 14
Event Viewer = no errors or other issues
2.) Not sure about stats or re-indexing by hand. I've only been at this new job for a couple of months.
3.) We pulled the heaviest queries out of a Trace and ran them in QA with no issues at all.
5.) Currently looking into the "reports in storage" option...
Thanks, Ben
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply