How can I reduce the overhead of watching client_names and subject_names?
Article ID: KB0086621
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
Problem: Whenever RTserver sends out watch status messages for client_names or subject_names, in addition to sending the name of the element that has just been added to the list or deleted from it it also sends the whole list of clients name or subject names. In applications with a large number of clients or subjects this can cause substantial overhead of data moving through the cloud.
There are two new optins in the RTserver that allow you to minimize this overhead.
They are; srv_subject_names_min_msgs and srv_client_names_min_msgs
The RTserver option srv_subject_names_min_msgs reduces the message overhead of watching subject names by not sending the entire subject table with each update. With the option set to TRUE, the subject table will be sent only once per server through the cloud at the time that the TipcMonSubjectNamesSetWatch is first issued. The first status message will contain only the subjects from the server that the monitoring client is connected to. As each server in the cloud returns it's own list of subjects, the monitoring client will be sent the merged list of subjects. After the initial list of subjects is sent, each individual status update will only contain the subject name that has been created or destroyed. A zero length string array will be sent in place of the entire subject table.
The option srv_subject_names_min_msgs is set to FALSE by default, so the complete subject names list will be sent with each status update.
The RTserver option srv_client_names_min_msgs reduces the message overhead of watching client names by not sending the entire client table with each update. With the option set to TRUE, the client table will be sent only once per server through the cloud at the time that the TipcMonClientNamesSetWatch is first issued. The first status message will contain only the clients connected to the server that the monitoring client is connected to. As each server in the cloud returns it's own list of clients the monitoring client will be sent the merged list of clients. After the initial list of clients is sent, each individual status update will only contain the client name that has joined the project (connected to an RTserver) or left the project (disconnected from an RTserver) . A zero length string array will be sent in place of the entire client table.
The option srv_client_names_min_msgs is set to FALSE by default, so the complete client names list will be sent with each status update.
Problem: Whenever RTserver sends out watch status messages for client_names or subject_names, in addition to sending the name of the element that has just been added to the list or deleted from it it also sends the whole list of clients name or subject names. In applications with a large number of clients or subjects this can cause substantial overhead of data moving through the cloud.
There are two new optins in the RTserver that allow you to minimize this overhead.
They are; srv_subject_names_min_msgs and srv_client_names_min_msgs
The RTserver option srv_subject_names_min_msgs reduces the message overhead of watching subject names by not sending the entire subject table with each update. With the option set to TRUE, the subject table will be sent only once per server through the cloud at the time that the TipcMonSubjectNamesSetWatch is first issued. The first status message will contain only the subjects from the server that the monitoring client is connected to. As each server in the cloud returns it's own list of subjects, the monitoring client will be sent the merged list of subjects. After the initial list of subjects is sent, each individual status update will only contain the subject name that has been created or destroyed. A zero length string array will be sent in place of the entire subject table.
The option srv_subject_names_min_msgs is set to FALSE by default, so the complete subject names list will be sent with each status update.
The RTserver option srv_client_names_min_msgs reduces the message overhead of watching client names by not sending the entire client table with each update. With the option set to TRUE, the client table will be sent only once per server through the cloud at the time that the TipcMonClientNamesSetWatch is first issued. The first status message will contain only the clients connected to the server that the monitoring client is connected to. As each server in the cloud returns it's own list of clients the monitoring client will be sent the merged list of clients. After the initial list of clients is sent, each individual status update will only contain the client name that has joined the project (connected to an RTserver) or left the project (disconnected from an RTserver) . A zero length string array will be sent in place of the entire client table.
The option srv_client_names_min_msgs is set to FALSE by default, so the complete client names list will be sent with each status update.
Issue/Introduction
How can I reduce the overhead of watching client_names and subject_names?
Feedback
Yes
No
Powered by
