My users are experiencing slowness in the system and sometimes cannot even load.
I noticed that my server is consuming 99% CPU.
When i further drill in, i realise the application pool worker process is running high. However, there is no request when i click in.
Anyone experience anything similar? The only major thing that we are working on it is creating a new company set up. Does that affect the performance?
What kind of resources do you have behind it? Do you have the minimum that Epicor lists in the hardware sizing guide?
Are you still on 10.1.400 ?
Yes, we have the minimum that Epicor lists in the hardware sizing guide.
Run Performance Diagnostics tool.
where is this tool?
10.1.400 has a memory leak on Entity Framework 4… you might want to upgrade.
If I recall the Issue was described as the following:
Entity Framework (EF) contains hard coded tuning levels that control the size of a compiled query cache. These compiled queries are a standard coding approach to speed querying the database with an upfront cost of preparing the query. These queries are cached to ensure the cost occurs only once.
Anytime EF exceeds the 800-count threshold, a new process starts in EF to count usage of all the queries for another hard coded value - an interval of one minute. Anything not touched in the last minute gets ‘aged’. After five increments, the query is removed from the cache.
With the hard coded 800 setting, ERP has been penalized for both repeatedly recompiling these queries as well as doing constant scanning to age and remove queries from the cache.
Epicor worked closely with Microsoft on getting this fixed in future EF Versions. Unfortunately 10.1.400 isn’t one of them. 10.2 should be a much better experience.
Hi Hasokeric,
Thank you for your reply.
are there any other solutions to resolve the high consumed CPU instead of upgrading? Currently in 10.1.400, we have done many module customization.
IDK if you can get an older new version, but our minor upgrade from 10.1.600.5 to 10.1.600.20, which we are currently on, fixed our memory leak problem back in March 2018. I don’t think it would require the same degree of change to customizations/dashboards/reports from your version at going up to 10.2 would.
Nancy
