If your Lotus Notes is using TCP, TCP's "ideal" receive window is the BDP (bandwidth delay product). For your 100 Mbps and 15 ms, that would be 187,500 bytes. How to adjust it, if it can be adjusted, depends on the host OS. (NB: many hosts default TCP receive window size is often less that 16 KB. Also older TCP implementations don't support TCP receive windows larger than 64 KB.)
BTW, this is only important for large data transfers. Client-server applications can be latency bound.
I think i do not have problems with the TCP-Windowsize.
Is it possible, that e.g notes for itself uses a kind of blocksize, which is independent from tcp-winsize and is smaller and so the whole communication (filetransfer) is slower, than it would be if it would use the whole tcp-windowsize.
It it possible Lotus Notes uses a blocksize that impedes its network performance? Sure, although I don't know if that's the case. Additionally, many client-server applications weren't designed for WAN latencies, and perform poorly across WANs. Lotus Notes might be such an application and there might not be anything that you can "tune" to improve.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...