Millions of Associations blowing up RAM

Hello Seasiders,

I am about to finish a portal website in Seaside 2.7 in VW5.

Currently, I am having massive problems with memory growth and through this with performance. After making some tests for about 15 minutes as a single browser user my image grows by about 40 MB to some 140 MB or more, which is mainly caused by some 1.800.000 or more instances of Association, which alone consume about 37 MB.

Almost all of these Associations look like this:
key: WAStateHolder(nil)
value: WAStateHolder(nil)

Again: This is produced in less than 15 minutes of browser usage by a single user!!!

At the same time there are only about 130-150 instances of WAStateHolder and when I tell them to "oneWayBecome: nil" the Associations are still not garbaged. I have no idea where this massive number of useless Associations comes from.

My questions:
1) Is this a known bug of 2.7, which goes away with 2.8?
2) If not, is the problem known and are there any solutions?

Thank you for your assistance. I will soon come back on this portal project with more details and performance considerations and I think this might potentially become one of or even the Seaside site with the most traffic.

Best regards
Frank

__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!
Mehr Infos unter http://produkte.web.de/club/?mc=021131

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Currently, I am having massive problems with memory growth and through this with performance. After making some tests for about 15 minutes as a single browser user my image grows by about 40 MB to some 140 MB or more, which is mainly caused by some 1.800.000 or more instances of Association, which alone consume about 37 MB.

This is not normal. There seems to be a problem in your code.

- How many objects do you register for backtracking?

- How many components do you have on one page?

- Are you sure not to re-instantiate components on every render pass?

- How many callbacks does an average page defines?

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Lukas,

thank you for your very quick response. I have to investigate the answers and that will take a bit of time as I had to take over this project from somebody else. I come back with answers ASAP.

Best regards
Frank


> Currently, I am having massive problems with memory growth and through this with performance. After making some tests for about 15 minutes as a single browser user my image grows by about 40 MB to some 140 MB or more, which is mainly caused by some 1.800.000 or more instances of Association, which alone consume about 37 MB.

This is not normal. There seems to be a problem in your code.

- How many objects do you register for backtracking?

- How many components do you have on one page?

- Are you sure not to re-instantiate components on every render pass?

- How many callbacks does an average page defines?

Lukas

_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside