Tariq Rashid <[EMAIL PROTECTED]> wrote:
> how do you mean? do mean that large number of active threads will kill my
> system?
A large number of "active" threads which are doing nothing other
than blocking for 30 seconds is a waste of resources.
> i dont see what is wrong with, say, 200 threads
>> Is this correct? If it is, it would make sense to have a threaded radius
>> proxy server as the forwarding proxy - perhaps with 3000 threads
configured.
>> It would then take 3000 delayed resoponses to fill exhaust the 3000
threads.
> Having 3000 threads waiting up to 30 seconds for a respo
Tariq Rashid <[EMAIL PROTECTED]> wrote:
> As I understand it - if I use a single-threaded radius proxy server - it
> will it have to wait for a reply from a proxied request before it can proxy
> a second and subsequent requests?
No. The server proxies the request, and then stops processing it.
We're considering using a front-end radius server instance as a proxy -
which will proxy depending on the user's domain name.
The question I have is to do with concurrency.
As I understand it - if I use a single-threaded radius proxy server - it
will it have to wait for a reply from a proxied re
4 matches
Mail list logo
