|Home » Technical Support » Elevate Web Builder Technical Support » Support Forums » Elevate Web Builder General » View Thread|
|Messages 1 to 3 of 3 total|
|Sun, Oct 18 2015 10:38 PM||Permanent Link|
I have performed an unscientific test of EWB's performance with a large query and the following are the results:-
App And Data In Same Computer:-
6 records = 0 seconds
40,268 records = 4 seconds
120,804 records = 12 seconds
App And Data Accessed Over A Network Wifi Connection:-
6 records = 0 seconds
40,268 records = 8 seconds
120,804 records = 20 seconds
I couldn't try it over a public Internet connection as I was stuck with a connection refused from the browser. Not sure why but I'll need to research it further.
I also tested clicking on the column header to have the data for that column sorted. It takes a while, especially for the 120,000 record query.
If there a way to call DisplayProgress() after the header column is clicked and then call HideProgress() after the sort is completed. I think the DisplayProgress() should be in the OnHeaderClick of the grid's column but where do I put the HideProgress().
|Mon, Oct 19 2015 4:14 AM||Permanent Link|
Frederick Chin wrote:
> 6 records = 0 seconds
> 40,268 records = 8 seconds
> 120,804 records = 20 seconds
Which pretty much confirms what everyone has always said, that you
shouldn't be showing a full database in a grid if you want a decent UI.
Remarkable that it is so good really, and the header sorting is
fantastic that it works at all in a browser, let alone as fast as
taking a while! 8-)
|Mon, Oct 19 2015 5:19 PM||Permanent Link|
Tim Young [Elevate Software]
Elevate Software, Inc.
<< If there a way to call DisplayProgress() after the header column is clicked and then call HideProgress() after the sort is completed. I think the DisplayProgress() should be in the OnHeaderClick of the grid's column but where do I put the HideProgress(). >>
Are we still talking about 40,000+ rows ? If so, then you need to consider reducing the number of rows. If a sort takes longer than a couple of seconds, then you've got too many rows in the dataset. In general, you *don't* want to be taking a long time performing operations like sorting in a browser because they completely tie up the browser's UI thread and prevent *anything* from occurring.
This is *now*, though. At some point EWB will have support for web workers, which operate like threads and will allow for this type of operation on unlimited numbers of rows without tying up the main UI thread.
This web page was last updated on
Thursday, March 23, 2023 at 02:07 AM
© 2023 Elevate Software, Inc. All Rights Reserved
Questions or comments ? E-mail us at firstname.lastname@example.org