search for: imperformant

...hared storage, export either a cluster filesystem or NFS, and have your dovecot servers mount that file system. Load balance these servers (Cisco ACE, ldirectord, ...) and there you go. Overall performance is limited by the speed of the shared storage and may further decrease due to locking issues, imperformant cluster filesystems and so on. 2) Set up every dovecot server with local storage and trigger a dsync after each change (pyinotfiy, incron, parse LMTP delivery logs, ...). Load balance these servers as before. Depending on the number of syncs that have to be done, mailbox replication may lag behind...

Ah, ok, "directory handle leases"... Ouch, I see... :-( In this case, I will first repeat my test scenario with a Windows SMB2 server and report back here. Based on the results of this exercise, you can then advise whether you still want to move this to smb-technical and raise this with Microsoft folks (who still might have a simple workaround "fix" to improve their SMB2

...erver request/response cycles over the network goes down - Wireshark pcapng file size is even slightly larger!!! (so it is NOT client-side caching on the Win SMB2 client side that does the trick), but the Windows SMB2 server "only" responds much faster to the infamous (and unnecessary/imperformant) SMB2_FIND_ID_BOTH_DIRECTORY_INFO requests with Pattern "*" - which probably means that the Windows SMB2 server does some caching here. In order to write the ~ 1000 files in my old test scenario, the total packet capture size for a SMB1 client against both a Samba or a Windows SMB1 s...