Hello,
I've searched the list and have been unable to find an answer to this question
so here it goes:

Using Cookies as session tracking method what sort of memory consumption per
connection will I be seeing (assuming it's all stored in RAM and not to disk
here since pound.cfg doesn't list a data directory).

I am assuming strlen(cookiename)+strlen(cookievalue) or some static buffer
size?
(+ related back end IP and maybe other stuff)  I could probably figure it out
by
grepping the source but having an answer in the mailing list archive is
probably
not a bad idea (I couldn't find one using "memory usage" or "memory
consumption"
as search terms)

I am suppose to set up pound on a machine that could possibly have 30,000
sessions tracked so I want to have an idea of what I'm getting into.

Thank you,
bdm

On Thu, 12 May 2005 10:34:18 -0400 gauze(at)dropdead.org wrote:
[...]

See the definition of the SESS structure in pound.h About 100 bytes per
session would be right (depending on your architecture).

As to tracking 30K sessions - allow me to doubt that. Assuming you use
300 seconds timeout that would imply about 100 NEW sessions per second.[...]