Within the doc page on limits.conf,
I found this entry regarding thruput:
[thruput] maxKBps = <integer> * If specified and not zero, this limits the speed through the thruput processor to the specified rate in kilobytes per second. * To control the CPU load while indexing, use this to throttle the number of events this indexer processes to the rate (in KBps) you specify.
This description leads me to believe that this specific option will limit the indexer thruput and might not work on the Forwarder to regulate it's thruput rate up to the indexer.
Can someone please confirm this is the case, or (assuming this is not the setting to use) tell me how to regulate the Forwarder's rate of thruput up to the Indexer?
I used this stanza to limit the thruput of Universal Forwarders and Heavy Forwarders towards the indexer. So I can confirm this is the setting you are looking for to regulate the Forwarder's rate of thruput.
We tested this behavior on a Linux and OSX UF and found that it did work to limit the bandwidth of the UF.
Hi, on a 4.3 UF the .../default/limits.conf states that maxKBps=0 . Does this mean that the throughput is unlimited? I think I remember reading that Light/universal forwarders were capped att 256 KBps transmission rates. Have I missed something?
If in the other hand want to speed your forwarders,
By example because the volume is high, or because the historical logs are large to tail the first time.
You can edit your own local setting to remove all limits.
by example in
or on the lightweight forwarder in
[thruput] # means unlimited maxKBps = 0
limits.conf doesn't exist in local. maxKBps = 0 is in limits.conf in default.
Total Indexing Rate - 331KB/s
Average Indexing Rate - 264 KB/s
You should never edit the default configurations. It is not found as you need to create one. You should create a new limits.conf within local which will supersede the default folder limits.conf values as required.