FYI to the devs: this method is now consuming a nontrivial amount of time under IE8. If I create 180 objects in IE8, the profiler shows toHashCode using 1200 ms. Yes, that is a lot of objects. But assigning hash codes shouldn't take longer than creating the objects themselves. :) I see a __postId suffix was added in QooxDoo 1.5, which makes this even slower.
Would it not suffice to just use a continuously incrementing number as the object hash code? The current code uses an array cache; arrays are not only slow in IE8, but they are notorious memory hogs. Dave -- View this message in context: http://qooxdoo.678.n2.nabble.com/qx-core-ObjectRegistry-toHashCode-is-slow-tp6798576p6798576.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
