I am seeing the following after updating my box to Trisul 2.0.

Thu Aug 25 12:37:24 2011.000394 DEBUG Pipeline context stats : queuedrop=6778,trypush=235131(2%)
Thu Aug 25 12:37:24 2011.002163 DEBUG Pipeline context stats : queuedrop=6170,trypush=233629(2%)
Thu Aug 25 12:37:24 2011.002660 DEBUG Pipeline context stats : queuedrop=7036,trypush=239445(2%)
Thu Aug 25 12:37:24 2011.002844 DEBUG Pipeline context stats : queuedrop=6636,trypush=237506(2%)
Thu Aug 25 12:37:24 2011.003148 DEBUG Pipeline context stats : queuedrop=5852,trypush=232277(2%)
Thu Aug 25 12:37:24 2011.004611 DEBUG Pipeline context stats : queuedrop=6079,trypush=236723(2%)
Thu Aug 25 12:37:24 2011.004676 DEBUG Pipeline context stats : queuedrop=6023,trypush=234392(2%)
Thu Aug 25 12:37:24 2011.006382 DEBUG Pipeline context stats : queuedrop=6261,trypush=233135(2%)


Any way to tune so I can avoid the drops ? I checked the documentation wiki but could not find anything.

Hi Larry,

The 2% number does not seem too high to me.

1. Trisul has an internal queue system, if you have memory to spare you can increase that number. To do so, change the QueueCapacity parameter in the config file to say 1000000 www.unleashnetworks.com/trisulwiki/docs/...:trisulconfig#tuning

2. Install the new builds just released today. It has major perf enhancements so this will probably go away.

Thanks,