Hi again Jim,
In my case I used the pool primarily for window instances, where each
class of window had lots of menus, toolbars, toolbar buttons etc.
Some window types had hundred of widgets, so it became expensive to
create new window instances dozens of times. Each new instance of a
class of window was exactly the same as any previous one, so it made
good sense to recycle used window instances.
Your case does sound a bit different to mine -- but pooling could
still work for you. If you are using thousands of Atom instances,
then you might try pooling Atoms. To make this work you may need to
use something like AtomFactory.getInstance() rather than using the new
operator to get Atom your instances. Then you need to extend Atom to
a PoolableAtom, or add a Poolable mixin to each Atom that the
AtomFactory creates. That way the AtomFactory can call a teardown()
each time an Atom instance is returned to the pool, and a setup() each
time an Atom instance is pulled out of the pool.
The result of all this is that the maximum number of Atom instances
that are ever created is equal to the maximum number that are in use
at any one time, rather than the sum of all instances that were ever
in use. If there is a significant difference between these two
figures, pooling might be worthwhile.
Of course, the above assumes that the root of the problem is that IE
fails to garbage collect disposed instances efficiently. I did some
intensive testing of this a couple of years back and found that IE6 in
particular had very unreliable garbage collection within the context
of a single, long running page (i.e., when the browser is never asked
to reload the page).
Cheers,
Simon
On Fri, Jul 4, 2008 at 1:13 AM, Jim Hunter <[EMAIL PROTECTED]> wrote:
> So how do you handle the scenario where one tool might have 20 Atoms on it,
> but the next iteration of that tool will have 1000? Do you simply just add
> new controls to the pool if needed allowing it to grow to the max size
> needed? Then when they are no longer needed, just set the parent to null? If
> I can't get what I am working on to solve the problem, I will look into your
> solution.
>
> Thanks,
> Jim
>
>
> On Wed, Jul 2, 2008 at 11:28 PM, Simon Bull <[EMAIL PROTECTED]> wrote:
>>
>> Hi Jim,
>>
>> I am not sure which version of qx you are using, but I experienced a
>> very similar problem a long while back with qx 0.6.x. My final
>> solution was to implement object pooling, and reuse pooled instances
>> rather than instantiating new ones all the time. I added my Pool
>> class to the contribute project, and (from memory -- must have been a
>> year ago now) I think Fabian migrated it to qx 0.7.x.
>>
>> Simon
>>
>>
>>
>> On Thu, Jul 3, 2008 at 10:52 AM, Jim Hunter <[EMAIL PROTECTED]> wrote:
>> > I am running into a troubling situation and am looking for a little
>> > help. My
>> > application re-uses 'tool windows' to display new information. It does
>> > so by
>> > removing all children (using a function I wrote to iterate through all
>> > children, destroy them (they iterate their children before destroying
>> > themselves). Then it destroys itself. Then I add the new contents to the
>> > tool window. In FireFox (all versions) I have no problems and the page
>> > renders in the same amount of time every time I bring it up. In IE (all
>> > versions 6-8), it takes longer and longer to render each time I bring up
>> > the
>> > tool window (I am using a qx.ui.layout.DockLayout as the main body of
>> > the
>> > tool window). And when I say longer, it goes from 2 seconds to 5 seconds
>> > to
>> > 9 seconds to 15 seconds to 25 seconds etc. It gets out of control very
>> > quickly.
>> > Has anyone come up with a way to manage this or even eliminate the
>> > problem?
>> > To me, it looks like the objects are not getting destroyed in memory and
>> > it's causing IE to start choking on them and doesn't release them as it
>> > should.
>> > Here is the function I use to clean out the tool before I add more
>> > objects
>> > to it:
>> >
>> > disposeChildren:function()
>> > {
>> > try{if(typeof this.hasChildren!='undefined')
>> > {
>> > if(this.hasChildren()==true)
>> > {
>> > this.forEachChild(function(chld)
>> > {
>> > chld.disposeChildren();
>> > chld.setParent(null);
>> > chld.dispose();
>> > qx.ui.core.Widget.flushGlobalQueues();
>> > });
>> > }
>> > }}
>> > catch(e)
>> > {
>> > try{this.setParent(null);
>> > this.dispose();
>> > }
>> > catch(e){}
>> > }
>> > }
>> >
>> >
>> >
>> > Any assistance would be greatly appreciated as we absolutely need to
>> > have IE
>> > working somewhat like FireFox. i know it's not going to work as fast,
>> > but we
>> > do need it to be consistant.
>> >
>> > Thanks,
>> > Jim
>> >
>> >
>> >
>> >
>> > -------------------------------------------------------------------------
>> > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
>> > Studies have shown that voting for your favorite open source project,
>> > along with a healthy diet, reduces your potential for chronic lameness
>> > and boredom. Vote Now at http://www.sourceforge.net/community/cca08
>> > _______________________________________________
>> > qooxdoo-devel mailing list
>> > qooxdoo-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>> >
>> >
>>
>> -------------------------------------------------------------------------
>> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
>> Studies have shown that voting for your favorite open source project,
>> along with a healthy diet, reduces your potential for chronic lameness
>> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
>
> --
> Jim Hunter
>
> DAILY THOUGHT: SOME PEOPLE ARE LIKE SLINKIES - NOT REALLY GOOD
> FOR ANYTHING BUT THEY BRING A SMILE TO YOUR FACE WHEN PUSHED DOWN THE STAIRS
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
