Dynamic Content

[Mone]

Hi,

how do you update your data provider?

Our VisualTable class extends the core ArrayCollection class.
Apart from the logic, to update the view we use something similar to this code:
<br /> //change the super class internal array to reflect the change. Note that arrayIndex is not <br /> //the same as itemIndex. It represent the position of the item inside the internal <br /> //collection. <br /> this.source[arrayIndex][fieldId] = newValue;<br /> //then notify the view to update to reflext the changes on the model<br /> this.itemUpdated(this.source[arrayIndex],fieldId,oldValue,newValue);<br />

Hope that helps.

[venkihere]

That with a couple of other changes helped in bringing down the cpu usage from 90% to 40%. Even a page that works with VisualTable takes same amount of cpu. But the memory usage was about 20% better than the NonVisualTable approach.

But I still feel 40% cpu usage on the client side is bad in either approaches. What could be wrong?

[Mone]

Hello,

Most of the CPU is used to show data on video. You could remove visual effects (if any), reduce the number of updates per second and so on to try to get better performance.

Please try to subscribe your NonVisualTables but remove every visual "notification" (i.e. just subscribe and use an empty NonVisualItemUpdateEvent listener). How much CPU is used?

With the NonVisualTable approach more memory is used because each item must be handled by 2 objects (the ArrayCollection and the NonVisualTable) and so some data is kept by both. The VisualTable extends the ArrayCollection and is written so there is no redundancy on data.

Moreover the Flash player uses a "step" approach to allocate memory from the system. See http://blogs.adobe.com/aharui/2007/0...nd_memory.html