Extreme Lag on Server Data Calls and Post-Simulation Updates

[SlinkyTWF]

Is it just me (I haven't seen anyone else mention this here or on Discord)...

...or is anyone else having substantial lag when the application tries to make a database call to load a player card for a pop-up? For about the last week or week-and-a-half or so, every time I hover a player link, the app locks up while it makes a call to the server to retrieve the data. This behavior lasts for several seconds each time the database call is triggered, and can repeat almost immediately upon hovering the same link, so I'm wondering whether it is a caching issue.

Additionally, transitioning from the Start Screen to the Overview Screen is sometimes taking well over a minute, as is loading simulation results, which creeps along for the entire 4.x MB of data. I timed the last attempt to enter the Overview screen from the Start Screen, and it took over five minutes, ostensibly because it was taking forever to download that .4.18 MB of data it loads every time I make that transition.

[NB]: I noticed that opening card packs also has a substantial delay, sometimes over thirty seconds.

For testing purposes, I reset the OOTP Settings to default, and the problem is persisting.

My ping, upload, and download speeds are all normal.
Other applications do not seem to be having these issues.
Simple restarts of both the app and of the OS do not affect the issue.
All three of my simulation teams have this issue, so it does not seem to be team-specific.
The OS does have the Windows 10 Summer Update applied, but I'm pretty sure the issue started after I applied it.
The OS is on an SSD, but OOTP is installed on a separate HDD.
System is well-over min spec, with 32 GB.
Diagnostics have not uncovered any obvious hardware errors.

I'm going to attempt to uninstall and reinstall the app after posting this.

[Update 1]:
Upon reinstall and system restart, I transitioned from Start to Overview in < 1 minute. There is a possibility that might have fixed or reduced the download lag, but I still get intermittent data call lag.
OOTP20 is having similar lag issues.
I am using the Steam version.

[Update 2]: After trying everything else, I went into the Documents/Out of the Park Developments/OOTP Baseball 21 folder and deleted everything. Currently, the data call latency has been reduced to about normal, but as correlation does not equal causation, I'll need to do additional testing before I can write this down as a troubleshooting use case.

[Update 3]: Spoke too soon. Started again about 4 hours later. An unusual symptom I've noticed is that my CPU fans spin up when it lags as described above, however, I don't see any dramatic rises in system resource use, only minor bumps in WiFi traffic, CPU Usage, and Memory Usage (the largest, at about 22%, which is actually substantial given I have 32 GB). Puzzling and frustrating all around, but if I'm the only one seeing it, it must be on my end. I can't rule out something like a pending HDD failure, but I don't see any issues with it when I diagnose the drive.

[Update 4]: Ultimately, I ended up disabling pop-up information. That at least kept my UI from locking up every time I moused-over a player name or team name, but the other latency issues remain, and now I have to click the player and go to their overview screen if I need to peruse their info. The only things I can figure are that they are either server latency, disk access latency, local data search latency, or some combination of all three. I do have a vast collection of cards (> 2800 unique cards), but the nigh-immediate onset of the problem dissuades me from giving priority to that as the source of the problem (it didn't start slowing down as the collection grew, it just started lagging out at once).

/shrug

[Update 5]: This morning, I updated my nVidia drivers to the latest version (456.38), and the problem has vanished. Correlation does not mean causation, but I was able to turn the pop-ups back on and they work normally, at least as I type this. If this was the cause, then the previous nVidia driver may have been buggy.