One is batch size (i.e. the number of entries that are batched and published in one visitIs the delay you are talking about on the sending side? If this is the case, doesn't this imply that the publisher is a polling thread - why would the publisher not be event driven off the backing cache? Or is it the case that you want to batch items to be friendlier to the network and were you to do this in an event driven style, you'd need some kind of timer thread to flush the buffer to the wire in case it took a long time to reach the high-water mark?
to the target cluster.) The other is the delay. How long does the Publishing Service sleep
before it wakes up to see if more stuff is around to be published.