Does anyone using it specially if you have a million record or you are using
workaround such as third party applications to handle large amount of data from the browser?
When dealing with large scale document models, and milions of records, i do not see a pourpose of showing ALL of them on single tree view...
( just imagine someone wants to punish you and orders you to :
SCROLL DOWN ALL ONE WILLION OF RECORDS how happy would you be ) :)
For that reason the views are limited to reasonable number of records, and leaving to user the choice of how many of them will be shown on single tree view...
I have tested that behavior on database witk 120k products...
Showing default number ( 80 ) per page gives fast page load,
but when i decided to show 2k on single page, it took something under a minute over adsl connection (4 mbit download)
After that I wanted to test view all 120k prodcuts on single page.. it took almost 4 minutes for page to load all data and render them into (html) view...
At the time I was just curious how fast will it work, but once i had the full view rendered, it took me a while just to scrol down that list....
Not to mention that it realy isnt productive to have so many data on single page.. (takes a lot of time to scrol up and down) ....
IMHO, Much better approach to hande large scale data is wise using and combinig filters and grouping in views to shorten the selection range of data and then show all (filtered/selected) data .
Hope this will be of help..
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 11/6/14, 9:24 AM|
|Seen: 978 times|
|Last updated: 3/16/15, 8:10 AM|