Re: athena eats my cpu

Hello Jean-Paul

Thxs for your time

>> Load: 1 client / one round
>> 1339223 function calls (1288601 primitive calls) in 178.951 CPU secs

>> Load: 3 clients / ten rounds each
>> 33541459 function calls (33103528 primitive calls) in 859.489 CPU secs

 >> 3 clients doing 10 rounds each, but your profile shows 4 times this 
 >> many
Eh?? 33541459 / 1339223 = 25.05
Not 30 because of the system becoming already slow (the figures are from 
a VMWare based BSD installation, clients on the same machine.

> Do your clients interact with each other, or are they each independent? 
Completely ndependent, if you want to have a look see

http://sf.jassportal.ch/differenzler?uid=gast

> You
> might also want to look at the actual payloads of the HTTP requests Athena
> is making.  There may be a bug where it sends more an more irrelevant or
> duplicate data as time goes on.  Firebug is somewhat handy for this kind of
> inspection.
Thxs for the suggestion, the amount of cumulated traffic in the browser 
is according to what we expect.

What I observe is that for every athena call I make I see several

appserver.py::handlesegment calls, which in turn creates in line 290 a 
new PageContext.
Q: why is every POST recorded as a new resource?

The context.py::PageContext.__init__ now updates the toremember attr and 
the one of my LivePage grows ad inifinitum and this is what is eating my CPU

So, LivePages should not have a toremember attr? But they inherit it 
from rend.py::Fragment()!

Thxs, Werner