Re: about large-web....tcl

[Haobo Yu <haoboy@isi.edu>]

How much is your interarrival time of per-object request? You should
estimate the average completion time of a single request, then find an
appropriate request interarrival. Otherwise, it's very easy to
dramatically increase the number of concurrent TCP connections and
packets, hence increase the memory usage. Be very careful of this 
parameter. 

Given that the TCP connection recycling is based on per-object request and
it worked well for single-object pages, I don't think that it has a
problem with multi-object pages. I've tested a two objects per page
version with long request interarrival and it takes the same amount of
memory as the single object case. This shows that the number of objects
cannot be a source of memory leak.

- Haobo

> I'm trying the "large-scale-web-traffic.tcl" example, seems that something
> wrong with it. It works very well (in terms of memory usage) when we
> specify that each page only have one object. However, when I increase the
> object/page (PageSize), it turned out that the memory usage boomed up very
> quickly. I tried to increase the average inter arrival time of objects,
> but still didn't help much. I suspect that there might be some problem
> with recycling tcp when there are multiple connections between the same
> source-destination pair. Since my knowledge in c++ and tcl is poor, I need
> someone's help, thanks.