Yeah, weâre very slow again right now.
Not prod, but Pilot is almost unusable atm.
Support has now re-reviewed my information and changed their conclusion to, yes its intermittently ridiculously slow, but it was before the linux migration too, so therefor its not a problem, but if it is a problem it must be due to our customizations.
I had no idea we used your customizations.
Itâs the first thing our users said after the update too, right @Francis ? It was slow.
FWIW, I agree with you both.
Yes, Epicor should have all the tools and data. Thatâs what we pay SaaS companies to do.
On the other hand, there are evidently performance issues to which customers are told âwe see no issueâ
One could wonder, Is that because they donât have the tools to see or some other reason
Anonymous evidence contributed voluntarily could add some transparency to the matter and help make change.
Love it @jbooker! I donât see how anonymous evidence contributed voluntarily wouldnât help. We can contribute AND ask them to start doing this monitoring on their own so we donât have to⌠a win-win.
Or they could reduce the MT pod density and increase the resources and make it easier for all to get on with our day jobs.
If Epicor is insisting people use their software SaaS then non of that should be needed voluntarily or otherwise. They need robust performance monitoring tools. You are all paying a premium for SaaS with the idea that it uses less I,T resource.
Per support they âchecked datadogâ and âeverything is fineâ.
Should we just throw a different thread up and post a poll?
do you think itâs slower after the upgrade: Yes? No?
I know how that goes, personally, itâs just show us the performance data then, the metrics that are showing itâs just as fast as before.
Idk what we are to do to get any help.
I mean support is not wrong. It was slow before the upgrade too. I donât really care to argue about whether or not its slower or it isnât. I just want adequate performance, period. And I am tired of arguing with my hands tied behind my back. As customers we donât have access to the data needed to truly diagnose what is going on behind the scenes, nor should it be any of our concern anyway. If we are saying Epicor, the system is not performant, they should be digging into that and resolving it not spending every ounce of effort telling us why we are wrong.
I had a former employer ping me yesterday. They said everything is slow and their BOMs have about 1000+ Materials per Job.
I told them good luck closing the month, because there will be End of Month issues we havenât found yet, and surely will come to surface in about 7 days.
Me neither @aosemwengie1, and thatâs where I think they misunderstand us.
Man. 
Part of the performance issue likely stems from indiscriminately appending .ToList() across the codebase without evaluating optimizations like .AsSplitQuery(). This forces the system to pull in excess data, which is especially problematic when existing Epicor logic relies on loop break; or continue; statements. Additionally, there may be underlying Cloud Ops misconfigurations, such as pending fine-tuning for container environments.
Given the pressure of production environments being down, it seems .ToList() is being used as a rapid hotfix instead of re-enabling MARS. I certainly donât blame the developersâthey are likely working 12- to 16-hour days right now to stabilize things.
However, from an architectural standpoint, a better fallback strategy would have been rolling back to Entity Framework 6 (or a stable equivalent) to allow the QA department to test the changes thoroughly. While skipping extensive testing for minor patches is understandable, a major release involving a new framework and OS requires much more diligence. Instead of rushing to maintain a two-week cadence for the 2026 release, they should have ridden out the 2025 version for another 6 to 12 months to ensure stability. There was simply no need to rush.
The codebase is huge, and it will take time while NOT UNDER PRESSURE to refactor properly.
I expect issues like this to continue for 10+ releases. Epicor isnât working on everything. They may know about issues, but its one of those âif no one complained, dont fix itâ.
It was a bold business move to make a less efficient ERP.
My #1 complaint from users is that itâs so slow. What took 2 minutes now takes 6+ what took 15 minutes now takes 25+. God help you if you have to click to a new screen