7 Second Delay after not using my DS1619+ (DSM 6.2.4-25556 Update 7) from Windows 11

[Fracas]

I've used this 1619+ for quite a while without many problems. After getting my Windows 11 box last year, I note that if I haven't accessed the Synology in a while (15 min? 30? 60?) the next access requires 7 seconds before the application (Explorer, etc.) updates.

I think sometimes when I hit the windows key and start typing an app to run (e.g., cal for calculator) even that sometimes freezes about 7 seconds. It's bad enough having the delay when I want to use the disk but I'm getting it even when I don't want to use the disk!

I don't think I ever saw this from Windows 10 or from Fedora 27-29-etc.

Any ideas on a Windows 11 setting or a Synology setting I could apply to fix this?

 

[Deleted member 5784]

This is

I think sometimes when I hit the windows key and start typing an app to run (e.g., cal for calculator) even that sometimes freezes about 7 seconds. It's bad enough having the delay when I want to use the disk but I'm getting it even when I don't want to use the disk!

This is nothing to do with your Synology. It could be caused by a drive spinning down after inactivity.
What drive (make, model) is your Win11 partition installed on? Is it a spinning HDD rather than an SSD?

 

[Fracas]

This is

This is nothing to do with your Synology. It could be caused by a drive spinning down after inactivity.
What drive (make, model) is your Win11 partition installed on? Is it a spinning HDD rather than an SSD?

Thanks for the interest, Fortran.

My Win11 PC has C: (and thus the whole OS partition) on an internal SSD. The Synology is mounted with \\diskstation\Whatever mapped to T: .

The specific thing you're referring to--the file name completion by the start dialog/menu--seems to be using a cache of recently-referred to binaries, which probably includes binaries on the T: drive.

May be a clue, but not directly related: something--either Windows or the Synology--is caching at least one level of files. If I haven't used the Synology in a couple hours, and go to look at a bookmarked folder in it, I'll see all the contents. If I then click on a subfolder, THEN I get the 7 second delay.

One thing I'm wondering is if there's some kind of search path for resolving a mount? Is it perhaps trying a bad IP address (perhaps because I might have used a different address for the Synology in the distant past) timing out, then getting the real name from a backup "nameserver" or something? Is that 7 seconds? I know Unix/Linux networking a bit better and recall something like that 20+ years ago.

 

[Deleted member 5784]

Thanks for the interest, Fortran.

My Win11 PC has C: (and thus the whole OS partition) on an internal SSD. The Synology is mounted with \\diskstation\Whatever mapped to T: .

Ok this eliminates the HDD spinning down theory on the WIn11 client.
Are your NAS HDDs set to spin down after a short time eg 30mins?
Are you by any chance using WD Green HDDs in your NAS?

One thing I'm wondering is if there's some kind of search path for resolving a mount? Is it perhaps trying a bad IP address (perhaps because I might have used a different address for the Synology in the distant past) timing out, then getting the real name from a backup "nameserver" or something? Is that 7 seconds? I know Unix/Linux networking a bit better and recall something like that 20+ years ago.

Could be a network issue to the Syno as you suggest. How are you creating connections to the Syno? I presume you're using a SMB mount - have you mapped a network drive letter to a NAS share(s), or are you just clicking on the NAS in the network section of file explorer and drilling down from there each time?
Are you connecting to the NAS via IP address (//192.168.1.n/sharename/) or by name (//myNAS/sharename/)?