Optimising NRPC Bandwidth Consumption for attachment Added by ~Bill Fezjipyskiakoi on May 5, 2011 | Version 1
|
NRPC port not consuming complete bandwidth. Noticeably on slow-er connections like 3G
|
This is a very sensitive area and I would strongly advice not make any such changes without proper diagnosis of the environment You connect Lotus Notes to a Lotus Domino server using a 3G wireless broadband line and notice that the NRPC port does not consume complete bandwidth. This is only visible with limited connectivity such as on 3G / ADSL lines and is not an issue in LAN environments.
You can make a comparison using network sniffer software using the same bandwidth on another protocol. Refer to the Comparisons.zip file in the Attachment section below to view comparison results between NRPC and HTTP. if you download an attachment from your mail file on the server. and if you monitor the bandwidth consumption by notes. you'll notice it uses a certain portion/percntage of it. Domino NRPC network traffic does not use up all available network bandwidth on Windows 32 platforms. This problem does not occur for Domino HTTP traffic on Windows 32 as all bandwidth is properly used.
- Problem is most apparent on 3G network connections - Problem seems a bit better on the UNIX platforms (AIX & LINUX). but does exist - Domino NRPC network traffic on Windows 32 platforms appears to be capped/limited to a certain threshold (which appears to be a percentage of total available network bandwidth).
The following workarounds were not successful.
-- Adjusting the operating system's TCP buffer sizes. Increasing these had a major impact on system/server performance with very little increase in bandwidth consumption.
-- Comparing both encrypted and non-encrypted network traffic.
-- Adjusting the TCP buffer of the Domino server. Details:
After a very thorough Internal testing SPR:FJAD84SJHM. was created and
The following parameter was added to the notes.ini file on the Domino server: SERVER_SEND_OBJECT_CHUNK_SIZE
The value of this parameter is set in bytes: 262144 -> for 256K 1048576 -> for 1 MB
The default value is 64K but you can adjust the values up to 256K or up to 1MB. The 1MB value must match the NRPC bandwidth consumption to any other protocol.
IMPORTANT NOTE: Use the above parameter only after considering other services and/or system resources.
|