*I only found ReadThrottleFilterBuilder in 1.1.0 API. What about Write ThrottleFilter?*
2007/4/30, Vinod Panicker <[EMAIL PROTECTED]>:
On 4/29/07, Paul Chen <[EMAIL PROTECTED]> wrote: > After curbing the read rate (one quota per acceptor) at a conservative rate, > the write problem is automatically gone. Not really. The read quota can be applied per acceptor, but the server might have connectors that could be writing to slower clients, leading to another OOM. > This is not an approach that leads to optimal performance, but just a way > to protect our Mina-based server not run into OOM. Using throttling is a solution that leads to better performance because the server can provide a good quality of service. Without throttling, all clients get affected because the server is not able to manage the incoming and outgoing data, resulting in an OOM. Regards, Vinod. PS: I was referring to DIRMINA-302 in my original post, not 132.
