Would there be any performance advantage to creating views in the same file as opposed to several different htmls?
I'd like to split them up into their own files in order to clean up my project a little bit, but I'm not sure if it would slow things down or if it's purely for organization.
Thanks!
I'd like to split them up into their own files in order to clean up my project a little bit, but I'm not sure if it would slow things down or if it's purely for organization.
Thanks!
6 Answers, 1 is accepted
0
Hello Ben,
There should not be noticeable delay when loading remote views. The difference is that ajax call is performed in order to fetch the content from the remote view, however on the local file system, this will be executed without any delays.
Regards,
Kiril Nikolov
Telerik
There should not be noticeable delay when loading remote views. The difference is that ajax call is performed in order to fetch the content from the remote view, however on the local file system, this will be executed without any delays.
Regards,
Kiril Nikolov
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0
Prem
Top achievements
Rank 1
answered on 11 Dec 2014, 08:33 AM
Hi Kiril,
I have noticed that loading remote views (in other html files) always lags in various devices I've tested.
Galaxy S3, HTC One, iPad Mini - Lags are 4-5 seconds, even if the view is small.
iPhone 6 - lags about 2 seconds.
On PC, the lag is about 1 second.
Is this normal with Kendo UI? Could we be doing something wrong?
For a large offline app, is it still advisable to have 1 single HTML file with 30+ views, referencing different sets of data?
What do you recommend?
Prem
I have noticed that loading remote views (in other html files) always lags in various devices I've tested.
Galaxy S3, HTC One, iPad Mini - Lags are 4-5 seconds, even if the view is small.
iPhone 6 - lags about 2 seconds.
On PC, the lag is about 1 second.
Is this normal with Kendo UI? Could we be doing something wrong?
For a large offline app, is it still advisable to have 1 single HTML file with 30+ views, referencing different sets of data?
What do you recommend?
Prem
0
Hello Prem,
It depends on individual preferences. When remote view is loaded the application will make an AJAX request to load the remote view, as they are both on the same device, it should not make much difference. In case you want this investigated, please open a separate support request and we will take a look.
Regards,
Kiril Nikolov
Telerik
It depends on individual preferences. When remote view is loaded the application will make an AJAX request to load the remote view, as they are both on the same device, it should not make much difference. In case you want this investigated, please open a separate support request and we will take a look.
Regards,
Kiril Nikolov
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0
Anthony
Top achievements
Rank 1
answered on 16 Jan 2015, 10:09 AM
Hi
I'm about to start something very similar, 1 page with 15+ views, my first thought was the performance is really going to suffer.
In normal scenarios the user will only want to look at say 4 of the views, hence I thought of remote views, so:
(1) Did you get to the bottom of this performance problem?
(2) At what point is the remote view loaded? Is it at startup or when the link is clicked on? For my scenarios I would ideally like a few views to have a rapid response as they will virtually always be clicked on, and the rest could in theory take a little longer.
thanks
I'm about to start something very similar, 1 page with 15+ views, my first thought was the performance is really going to suffer.
In normal scenarios the user will only want to look at say 4 of the views, hence I thought of remote views, so:
(1) Did you get to the bottom of this performance problem?
(2) At what point is the remote view loaded? Is it at startup or when the link is clicked on? For my scenarios I would ideally like a few views to have a rapid response as they will virtually always be clicked on, and the rest could in theory take a little longer.
thanks
0
Prem
Top achievements
Rank 1
answered on 18 Jan 2015, 10:44 PM
Hi Anthony,
FYI we decided to have all views in the 1 html file. We noticed it improves performance significantly. For older devices, there is a slight lag but it's acceptable for us. With multiple html files and views, everything is loaded up initially as per the manifest, but in our case, we were populating the views from local application cache and this was causing delays when remote views are called. With everything in 1 html file, it's fast.
IMO if your views are pre-populated and static then you should have no issues with remote views.
Do not assume or just read documentation. Always test before you implement is a lesson learnt.
Prem
FYI we decided to have all views in the 1 html file. We noticed it improves performance significantly. For older devices, there is a slight lag but it's acceptable for us. With multiple html files and views, everything is loaded up initially as per the manifest, but in our case, we were populating the views from local application cache and this was causing delays when remote views are called. With everything in 1 html file, it's fast.
IMO if your views are pre-populated and static then you should have no issues with remote views.
Do not assume or just read documentation. Always test before you implement is a lesson learnt.
Prem
0
Hello Anthony,
the local views and their containing widgets are instantiated on demand - the first time the user navigates to them. Also, the datasource components are not requested until the data bound widgets are instantiated. In a nutshell, This means that having multiple inline views does not affect the performance of a mobile application in any way.
Regards,Petyo
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!