Using SmartGWT-4.0 (released Jul 05, 2013), browser is Chrome v. 31.
While tracking down performance problems within a rather complex SmartGWT application, I noticed that a significant amount of time is spent somewhere inside the Canvas.getChildren() method call. I looked at the source code for that method, and this is using ConvertTo.arrayOfCanvas().
Most of the time is spend doing a call to obj.getAttribute("__ref"), which apparently creates a string representation of something, and compares that with null. It seems to me there might be more optimal ways of doing this check.
While tracking down performance problems within a rather complex SmartGWT application, I noticed that a significant amount of time is spent somewhere inside the Canvas.getChildren() method call. I looked at the source code for that method, and this is using ConvertTo.arrayOfCanvas().
Most of the time is spend doing a call to obj.getAttribute("__ref"), which apparently creates a string representation of something, and compares that with null. It seems to me there might be more optimal ways of doing this check.