This topic has me concerned with a couple queries I've been working on recently. I'm working on a Windows Presentation Foundation (WPF) app. We use Entity Framework (EF). (I know that EF has a bad rep within the DBA community, but trust me, we developers are still going to use it.) The query I've most recently been working on is complex. The spec requires me to return the values from a table, a couple of child tables and a grand-child table. The EF code works, but under certain circumstances it takes a long time to return results. There are reasons for this such as I'm running this in the Visual Studio debugger (any debugging operation is inherently slower than it will be in production). Also, when I've noticed this unacceptably slow behavior, I've encountered it while testing the app on my work laptop at home. (At this point I'm still working from home.) If I remote to my desktop in the office this behavior isn't as noticeable.
However, I am concerned it might be bad for any users who would be farther from our servers. This is hard for me to judge, but at least I get an idea of what it might be like while WFH. My home is about 70 miles from the servers. For my state I've got fast Internet connectivity, so it surprises me how long it takes the query to run. It doesn't time out, as in all the testing I've done over the last couple of months I think I might have encountered a timeout error only once. I'm also sure that a large part of it is we're using older versions of the .NET Framework, EF, etc. Upgrading would certainly help noticeably, but that's unlike to happen. There's no easy answer here.
Kindest Regards, Rod Connect with me on LinkedIn.