.Net Core 3.0 WPF Dreadfully Slow

5 posts, 0 answers
  1. Wayne Williams
    Wayne Williams avatar
    38 posts
    Member since:
    Jul 2019

    Posted 03 Oct 2019 Link to this post

    Hi,

    I have an Telerik WPF app built recently for .Net Framework 4.7.2. The app is lightning fast and I couldn't be happier with performance.

    However, I just successfully converted it to .NET Core 3.0, and while the app functions properly with no compile or runtime errors, its performance is dreadful. For example, launching the .exe takes 1.5 seconds for the .Net Framework version, but 21 seconds for the .Net Core version. A simple database query takes .01 seconds (i.e. to both retrieve the data and refresh the interface) in Framework, but 6 seconds in .Net Core.

    I'll investigate and identify the components causing the problem, but do you have any opening thoughts that might point me in the right direction?

    Wayne

     

  2. Wayne Williams
    Wayne Williams avatar
    38 posts
    Member since:
    Jul 2019

    Posted 04 Oct 2019 in reply to Wayne Williams Link to this post

    Tracked this to 1 issue, thankfully. Using an in-memory database. Calling conn.Open(), where conn is essentially a DbConnection.

    In .Net Framework 4.7.2, that call only takes a few milliseconds.

    In .Net Core 3.0, it takes over 2 seconds. So, it appears the problem is with the in-memory engine, not anything to do with Telerik.

    Wayne

  3. Martin Ivanov
    Admin
    Martin Ivanov avatar
    2425 posts

    Posted 04 Oct 2019 Link to this post

    Hello Wyane,

    Thank you for sharing the cause for the slow performance. If you find any solution for this, you can share it too. I think this will be useful for others that hit the same issue.

    Regards,
    Martin Ivanov
    Progress Telerik

    Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
  4. Wayne Williams
    Wayne Williams avatar
    38 posts
    Member since:
    Jul 2019

    Posted 08 Oct 2019 in reply to Martin Ivanov Link to this post

    This has to do with DNS resolution of Localhost and is apparently a bug in the .NET Core 3.0 release. Short story is that if you change the host reference to 127.0.0.1 instead of Localhost, everything behaves normally.

    You can follow the issue here: https://github.com/dotnet/corefx/issues/41588

    Wayne

  5. Martin Ivanov
    Admin
    Martin Ivanov avatar
    2425 posts

    Posted 09 Oct 2019 Link to this post

    Hello Wayne,

    Thank you for providing this information. I am sure that this will help someone. As a small gesture of gratitude, I've updated your Telerik points.

    Regards,
    Martin Ivanov
    Progress Telerik

    Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Back to Top