I have an application using xamWebGrid and in the demo configuration it displays just 357 rows. The data are instances of a simple CLR object of 11 properties of value types: datetime (3), enum (2), string (2), int (2), bool (2).
The empty grid is displayed quickly but the time from setting the data source to displaying the data is ~5 seconds. Initially this is quite confusing for users who are unaware they should wait so press F5 to refresh the page. We've put in a "Loading..." message on screen to inform the user but there does not seem to be an event fired by the xamWebGird once the data is displayed. Without such an event we don't know when to remove the loading message.
So two questions: why the delay? There is not a lot of data. Secondly, is there an event that will fire once the display is presented?
Thanks
Bill Seddon
Hi Steve
Thanks for the news about the performance improvements. We updated our software to use 10.1 and believe we are seeing an improvement in the time to render the display (after the data has been retrieved) from ~5 seconds to ~1 second. So good job.
Bill
Hi,
Just as an update, 10.1 was released a couple days of ago, and we added a lot of performance improvements to the grid, specifically in loading. These enhancements weren't just made in 10.1, they will also be in our next 9.1 and 9.2 Service Releases.
-SteveZ
And I hope anyone else experiencing an presentation performance issue also see an improvement bit I'm guessing you are looking at different problem.
We were alerted to the issue by a user (usinga publicly available release build) who had difficulties which arose from impatience at the time taken to display rows. We see no material difference in performance between release and debug builds.
I was amazed by how slow the grid was performing (running from Visual Studio). As a test, I published out the web site and ran it outside the debugger and it was SO MUCH FASTER !!
You do offend me, go hijack another post. The problem is NOTHING to do with the backend. Its to do with the number of objects the grid is placing in the visual tree regardless of the source. In my case the source is Xml but in the test cases provided it is in memory. You can't beat that.
Let me say again - because your posts are potentially misleading others with the same issue - this has NOTHING to do with the backend (and I include the datasource in that definition).