We recently deployed a .NET Framework 4.7.2/Microsoft.Owin 4.0.1.0/Episerver 11.23.3/Episerver.Commerce 13.15.0 application to DXC. We also integrated ADFS with episerver.
Unfortunately, we’re seeing very inconsistent response times login to CMS – sometimes fast and some time very slow and peak CPU 100%. The same application running on a VM takes very less than response time and consume small amounts of CPU.
Initially we assumed it was slow database/Episerver Find query performance, but after doing some profiling it appears the queries actually run quickly and most of the time appears to be in “external code”.
Specifically, it appears that most of the time is spent in the OWIN request handler code:
Has anyone experienced issues using OWIN in DXC? Is there special configuration or code changes needed?
Very late reply, but as Middleware, you'd be seeing Owin everywhere. Slow performance is, in most of the case, caused by something else underneath. You should reach out to developer support as an analysis of the profile traces is needed.
Hi,
We recently deployed a .NET Framework 4.7.2/Microsoft.Owin 4.0.1.0/Episerver 11.23.3/Episerver.Commerce 13.15.0 application to DXC. We also integrated ADFS with episerver.
Unfortunately, we’re seeing very inconsistent response times login to CMS – sometimes fast and some time very slow and peak CPU 100%. The same application running on a VM takes very less than response time and consume small amounts of CPU.
Initially we assumed it was slow database/Episerver Find query performance, but after doing some profiling it appears the queries actually run quickly and most of the time appears to be in “external code”.
Specifically, it appears that most of the time is spent in the OWIN request handler code:
Has anyone experienced issues using OWIN in DXC? Is there special configuration or code changes needed?
Regards,
Thang Le