|
Roberto Nibali wrote:
>
> Hi Joe,
>
> > It would be nice if the director didn't crash when the number of connections
> > got large.
>
> I don't exactly know where there is the misunderstanding but the director
> never crashes because of exhaustion of memory.
Let's say you fill up RAM with the hash table and all user processes go
to swap, then there will be problems - I don't know what, but it doesn't
sound great. I expect we need to leave a certain amount for
user space processes and not allow the director to take more than a certain
amount of memory.
> Not that I would know of but you could use my treshold limitation patch :)
Maybe I'd better go grab it.
It would seem that we need a method of stopping the director hash table from
using all memory.
> 128MByte, persistency 300s:
why does the persistency timeout affect the number of connections?
It affects the number of users that can be connected at any time.
> max amount of concurrent connections: 3495.
> We assume having 4 realservers equally load balance, thus we have to
> limit the upper threshold per realserver to 873. Like this you would never
> have a memory problem but a security problem.
what's the security problem?
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
