Good afternoon, I work for an MSP and we manage IT for a client that recently migrated from an on-prem environment (RDS + file server in the same rack) to Azure Virtual Desktop. Since the migration, QGIS performance has degraded when opening and saving certain datasets/projects. Environment
* QGIS version: 3.40.12 “Bratislava” * Azure Virtual Desktop (multiple session hosts) * Data stored on Azure Files / Storage Account (Premium), same region as AVD * Access via Private Endpoint (no public internet path to the storage) * First days after migration were OK, issues became noticeable after a few days Symptoms * Opening and saving files is slow and sometimes appears to hang * For one specific dataset/project, QGIS crashes on open or on save * Windows Explorer also becomes “Not responding” when opening/saving that same file set (seems I/O related) * Other files can also feel slower, but the reported file is consistently problematic * The file that seems to hang the most is a 2 mb file What we are looking for * Are there known QGIS settings, data formats, provider options, or project configurations that can cause heavy file locking / long blocking I/O over network storage? * Any recommended best practices for running QGIS in a VDI/remote desktop setup with data stored on network file shares (Azure Files), especially regarding caching, temp directories, or avoiding certain workflows? * Any logging or diagnostics you recommend (QGIS logs, GDAL/OGR debug options, crash dump locations) that would help narrow down whether this is QGIS-related vs storage/SMB/locking/latency? Thanks in advance for any guidance. Muki Lukuna IT Cloud Engineer @ IT Synergy [cid:itsfooteremail_e344558a-1941-4773-bd69-a10ea4ce26fc.png]
_______________________________________________ QGIS-User mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
