NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Howdy LDM Users/Unidata, I'm attempting to get straight in my head some relay latency between a LDM server and client. Both are running the current release, 6.14.5. My simple test is as follows, on the LDM upstream pqinsert something every two seconds on the LDM downstream, monitor receipt of these inserted products via `ldmadmin watch` and also putting the LDM client connection into debug mode to see what the RPC is doing. What I observe appears to LDM batching the RPC calls every 30 seconds instead of a more timely relay of inserted products to downstreams. My typical naive and likely wrong understanding of LDM's code is that this is controlled by: src/registry/globals.c /* * Time to sleep in pq_suspend() and before retrying connects. */ unsigned int interval = 30; So my questions: 1) Is this latency a function of my usage of `pqinsert` on the server side instead of some proper LDM forked child process? 2) Are there side effects / significant performance concerns of setting the `interval` value above to some lower threshold? I am thinking about setting it to 1 or 5 seconds. Do I need to be careful to change this on all my LDM servers and clients in my local topology? 3) Is there some other setting that controls this batching of RPC from the server to the client? thanks and Happy 4th! daryl
ldm-users
archives: