panyasan wrote:
>
>
> benco wrote:
>>
>> About databinding... As Martin mentioned, I wonder if the qx.data.Array
>> could work with the actual structure... as it potentially slows the
>> processes.
>>
>
> I haven't found time to do any test on that, but I wonder... Internally,
> the qx.data.Array uses a normal native array, on which it operates. except
> for the event-firing stuff, why would a "big" qx.data.Array be so much
> slower than a native one? I guess we would need some performance tests
> that compare the two.
>
>
I just changed the demo to use 100.000 "spam messages". To generate them,
you need a nested loop with timeouts:
var x =0;
for (var j = 1; j < 100; j++ )
{
qx.event.Timer.once(function(){
for (var i = 1; i < 1000; i++)
{
dataModel.addLeaf(te, "Spam Message #" + (x++) );
}
},this,0);
}
otherwise there will be a script timeout. But once they are generated, the
tree works very well, without any noticeable delay, except when you prune
the node containing the 100.000 nodes (script timeout in Safari, Firefox,
and Chrome) - which might happen just as well with the native array
implementation.
So even when I don't have exact tests, I think this casts doubt on the
thesis that qx.data.Array doesn't work well with huge loads of data.
Cheers,
Christian
--
View this message in context:
http://n2.nabble.com/qooxdoo-contrib-cometd-Dialog-and-VirtualData-tp4247446p4252460.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
