It’s my first time posting here. I’ve been using these forums quite a lot recently as we started using Kinetic in June, there is a lot of helpful info out there.
We are experiencing very slow SSRS reports (such as Order Acknowledgements), the base reports are typically 20 seconds or longer, sometimes up to a minute. Our custom reports are even slower (often over a minute).
It feels a very long time to wait when running multiple reports, I don’t know if this is normal. I wanted to check how long SSRS reports typically take for other companies using Kinetic. We are using the cloud version, I would be interested to hear how long it takes for both cloud and on premise version. Would a few people be happy to share their timings?
First off, welcome! I hope this site is useful for you, I know it has been for me.
Are you generating the reports in the browser or the client? I have noticed that the browser takes a bit longer, as the reports have to be sent to the edge agent.
20 seconds for base reports and 1 minute for custom reports is a lot longer than what I experience. Although a few months ago a lot of Epicor customers were having issues with SSRS reports either not working or being very slow. IIRC this was something to do with Microsoft changing something, but I am not sure.
Hi, give the SysTasks dashboard a try, I made this for helping to diagnose SSRS issues. It shows the parameters used to generate a report, works cross company, and has other nice-to-haves vs. the Epicor System Monitor.
SSRS Generation/Preview generally takes under 10 seconds on Epicor side for OOB reports, but it depends on which report, some like JobProd are very heavy on RDD side out of box.
SSRS is client/server architecture against Epicor’s app server, so there is a whole other set of resourcing challenges faced on SSRS side. And it is set up 1 SSRS : Many AppServer, so you contend resources with other customers. Challenges can arise during high load times.
We have an open SSRS case for several months which is tangentially related to performance issues (load is sometimes so high that concurrency issues are encountered - more resourcing was thrown at our SSRS server as a bandaid)
Thanks for the quick responses! I’m glad to hear this isn’t the norm, because hopefully something can be done to reduce the times. It’s getting passed between support and developers at Epicor at the moment so we’re not making much progress.
We’re using the browser, the client won’t be around for much longer.
It’s been the case for us since we started with it in June.
Thanks for the link Gabe, I’ll have a look. How long does a job traveller take for you?
Looking at a sample of runs today, it is dependent on company size.
For a smaller company - 4 seconds for out of box JobTrav ReportStyle 1001
For a larger company - 7-10 seconds.
I am only counting time from the “StartedOn” and “EndedOn” parameters in SysTasks - at that point pdf is rendered completely on server time - handoff to user should be nearly instantaneous (within 2-5 seconds of “EndedOn” - on either browser or smart client. (assuming they aren’t doing anything weird like running smart client on same account at the same time, which can make things go weird - it will popup in an indeterminate location then and may be delayed)
Switching companies can impact report display time (not generation, it will still generate within 10 seconds, but not pop up for extended period of time) - I also have an open bug tracking that issue as well.
That’s working a bit differently in 2025.2 - browser tabs are now making requests to Ice.BO.SysMonitorSvc/CheckForTaskUpdatesKeepIdleTime every 30 seconds, at an IO rate of roughly 5 KiB per minute per tab, previously it was over 4 MiB per minute per tab. 5 KiB per minute per tab isn’t good performance, but at least it’s on a normal scale of inefficiency.
Doesn’t improve browser client latency, though. We’re still stuck with an absolute minimum latency of 0-30 seconds.
This is going to sound really dumb, but one thing that made our reports run faster was uploading the files through the classic version of report style in the client version. I have no idea why that would work but you can try it and see.
Welcome to the group!
We have worked hard to also reduce print times, and are in the Cloud.
What we have done was to set up the Network Edge Agent on our Print Server, and then add the Printers there and map the user to the Edge Agent Network Printer instead of the Edge Agent using the Local Printer. That cut it down from 30 seconds to about 8 seconds.
We also found a setting from support that helped with the “Spinning” helicopter blades when printing, becuase Epicor/Windows is searching for Network Printers when they click Print. It is under Company Maintenance, and is on the Reporting Card, called “SSRS Printer Option” and set that to “Client Printing Only” so it does not try to search the Network for Printers. That also sped up the user experience because the 1st time they printed, they had to wait for the “Spinner” to stop and that took 30-60 Seconds on the 1st print of the day.
Hope this helps as well.
Thanks George, it’s even the Print Preview that is slow so we’re focused on reducing that then we will compare against the printers. We also have the Network Edge Agent setup on our print server so hopefully that side will be ok.
Just wanted to update you on this. We’ve tested uploading the reports via the smart client instead of the browser and on one report it dropped from 10 seconds to 3 seconds. I can’t understand why that make such a huge difference, but a big thank you to @Taylor_L for the tip!
Thanks also to @GabeFranco for the dashboard, I used it to create a BAQ to help log the times.
We still have some improvements to make but it’s a big step forwards. Thanks for your support.
