Nice work!
I assume in order to implement it, it would require dynamic content compression installed in IIS?
Correct, however I would hold off until Epicor comes back with final guidance.
There is a bug in .net 4.8 decompression that under certain conditions is causing some issues. As Jeff said they have a solution for it but weāll need some direct guidance to properly implement
5 Likes
Nice, looking forward to hearing the solution.
I wanted to give a final update on this. There were code changes needed to resolve the intermittent deadlocks. Those changes will ship with 2023.2 as well as 2023.1.15.
For 2023.2, RPC compression will be enabled out-of-the-box.
For 2023.1, RPC compression will continue to be disabled by default due to the complexities of updating a web.config on an already installed environment. Once you have 2023.1.15, you can enable compression by manually changing your web.config to add:
<add mimeType="application/x-epicor-erp-rpc" enabled="true" />
JSON and XML compression as used by the web client among other places already was and will continue to be enabled on all supported releases.
Thanks everyone for the feedback here, especially @josecgomez. And kudos to @JeffLeBert for leading the effort to find the elusive deadlock.
8 Likes
Thanks Santiago and @JeffLeBert 
Really appreciate you guys jumping on this and getting it solved it is a huge improvement in performance 
3 Likes
And for cloud customers?
Did you already put something in place for 2023.1.9?
I imagine you can ask via a EpiCare ticket but weāll be on 2023.2 soon enough so weāll probably just wait.
Itās not clear if its going to be enabled for cloud customers on 2023.2 or for that matter anybody upgrading from 2023.1, the statement above sounds like its only going to be enabled automatically for new installs.
1 Like
Thatās not the way I read it, I assume it will be part of the upgrade process.
but you know what happens when you do thatā¦
Cloud will be upgraded on 2023.2 soon (pilot upgraded already).
So if I am going live on 2023.1.9, thereās nothing I can do right now to fix this?
1 Like
Come on @utaylor live on the wild side and jump to 2023.2.
Is it out yet for on prem in the next week? Maybe Iāll go even wilder and just go live on that and not tell anyone. No UAT, no nothing.
1 Like
Are there plans to release this for 2022.2? We just went live on 2022.2.16 (On-Prem) at the beginning of October and all of our remote facilities are having performance issues. The primary complaint is slowness when creating records (issuing material, adding charges to a Sales Order, creating Pack Slips in Customer Shipment Entry).
I have a call open with support on the issue, and I have pulled Client Trace logs from those facilities and given them to support. The NetworkTransportTime is what support and my team have noticed in comparison to Epicor 10. We are not seeing any issues at headquarters where the appservers are located.
Iāve read through this string and couldnāt really tell if this only affected users over WAN or site-to-site VPN connections, so Iām not sure if this fix would provide any relief to our remote facilities.
Yes it is a distance / badnwidth issue so Site to Site VPN would be affected by this if your clients from the remote facilities are going from there to your server (in another state) this would / could provide relief.
You may have to request a one off and see if theyāll make it for you.
1 Like
At this time there are no plans to implement this in releases prior to 2023.1. But you can certainly make your case with support for consideration.
2 Likes
We upgraded to 2022.1.21 in April, and support told me the only workaround would be to upgrade to a version where this is fixed natively. I tried.
They should support all versions that havenāt reached EOL.
3 Likes