You’re offline. This is a read only version of the page.
430
Hello,
We have been experiencing problems, since we installed the program, with extrememly slow performance in opening and viewing reports in MR 2012. It takes a few minutes for the program to open and it takes some time for a report to open. We have a good amount of reports that we use in our organization and a folder structure setup for each of the entire company. Has anyone else been experiencing issues with Management Reporter and what have you done to correct these issues? Thanks for your help.
*This post is locked for comments
Ryan,
I recorded a video of a report generation to see how things break down.
1. Time from when you click the generate button until the Queue screen is open: 0.7s
2. Time from when you see a report as queued until it starts processing: 5.97s
3. Waiting for processing (Time until status changes to complete): 6.42s
4a. Time before the viewer splash screen is displayed: 0.05s
4b. Time after the splash screen is displayed until the viewer is open, but the report has not yet loaded: 2.25s
4c. Time from when the viewer is open until the report is actually loaded and accepting input from the user: 1.83s
Hi Marc,
If you have a few extra minutes can you help me understand how your timing breaks out into the following:
1. Time from when you click the generate button until the Queue screen is open
2. Time from when you see a report as queued until it starts processing
3 -Waiting for processing
4. Waiting for the desktop viewer to launch
I'm curious if most of your time is on steps 1-2, and 4. The Drilldown viewer was very light weight and processing was done on the client so FRx really didn't have to use these steps.
The data mart is definitely faster than how FRx retrieved its data. However in your example, a <30 second report doesn't look like it will see any improvements since it is not a complicated report and it does not run long enough to take advantage of our optimizations.
Thanks
Ryan
I tested out MR 2012 RU4 and the data mart integration on our system. I didn't see any improvement in report generation times. The data mart and legacy options both were measured at about 18 seconds from the click of the "Generate" button until the report viewer fully loaded. FRx still does the same report in 3 seconds.
I guess that makes sense. The report I've been testing with isn't too terribly complicated. Plus, if the data mart were going to provide dramatic performance improvements, I would have expected the FRx reports to be running just as slowly since FRx also doesn't have a data mart option.
Check out the latest coming in RU3
OK. I set up a test environment for MR2012ru2 with 16GB RAM and 4 cores @ 2.67GHz running Windows Server 2008 R2.
For comparison purposes, the times with the less powerful hardware that I've been using are:
Management Reporter: 19 seconds (from Generate click to report visible in Report Library)
FRx: 3 seconds (from Generate click to report visible in FRx DrillDown Viewer)
On the more powerful system, the time is:
Management Reporter: 16 seconds (from Generate click to report visible in Report Library)
So, we gain 3 seconds with the more powerful hardware. Now, I realize that 16 seconds isn't too terribly long in the grand scheme of things, but it's over 5x slower than FRx and it crosses the threshold from feeling instant to something that feels like a wait.
This makes MR a hard sell to the users who just want to quickly run financials for their month end packages because it becomes a case of "generate, wait, print, generate, wait, print, generate, wait, print". Or, if we advise them to create a report group, then it is "generate, go get coffee, print".
I recently mentioned this issue to one our partner's reps and he told me that MR being slower than FRx is something he consistently sees at every client site where he upgrades the site to MR.
Also, there are a few entries that were submitted to Microsoft Connect about about speed issues, such as :
connect.microsoft.com/.../management-reporter-generates-too-slow
and they are all closed with the resolution of "Won't Fix".
Ryan, would it be possible for you to get one of these opened back up? The "Won't Fix" designation kind of communicates to us that the development team is content with the speed as is.
FWIW, our server runs both GP and MR. We have 32GB of RAM, with multiple Xeon 64-bit processors. We have no issues with GP response times, just Management Reporter generation times. No issues with viewing previously-generated reports, either. The generation times are uniformly slow - with anywhere from zero to 10 users active in GP.
Hi Marc, In the latest system requirements (with rollup 2) says the recommended Process server RAM is 12GB or higher, Application is 4GB or higher. The process server had been recommended at 4gb but it's changed now.
Good Luck, let us know how you make out.
Tracy
Tracy, the process server and application server are running on the same box. The RAM is 4 GB. I see that this is under the "Recommended" specs for MR, but the server is indicating there is 1.3GB free and my performance testing has been with only me generating reports. I'd expect the recommended specs take multiple users into account. However, my next text will be on a really beefy server to to see if there is a difference.
Ryan, I guess you are right. The OP looks like it was talking about loading already-generated reports, but the first comment the next day by "bcool" directed the conversation toward the entire process of generating and loading reports on demand and a discussion of the speed vs FRx.
I see there's another thread that seems more on point and I will look to watching that one instead.
I had considered opening a support case regarding MR's performance issues, but have been unable to find any users making the claim that MR speed can match FRx. If I thought there was a problem with our implementation, I would open the ticket right away, but all the results a Google search produces involve complaints about MR's speed and how much slower it is than FRx.
Your suggestion of opening a support case for the pure effect of encouraging the developers to fix the speed problems plaguing all users is interesting, but I'm skeptical. I've been through the MS support machine for Windows Server before. In that case, I had to fight with reps who tried numerous times to close the case with the explanation of "working as designed" even though, ultimately, the case revealed a bug and we were issued a hotfix and a refund for the case charge. That was for an issue that cripled the system. This is a case of a product running slower than expected. I just can't imagine a case of this type getting any traction.
This thread was created to address performance related issues to opening and viewing reports from the report library, not report generation.
If you are having performance issues with reports make sure that the report design makes sense and that you are not including more detail than what you need. We do try to make some improvements each release regarding performance but those may not impact every customer for every version of Dynamics ERP.
I would still recommend logging a ticket with support if you are seeing slow report generation times, as we can't fix issues we don't have details on.
Thanks
Ryan
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (