Kendo UI upgrade wizard very slow for ASP.NET MVC

16 posts, 0 answers
  1. CORNEL
    CORNEL avatar
    44 posts
    Member since:
    Jan 2012

    Posted 15 May 2013 Link to this post

    Hi Guys!

    I'm curious why the Telerik upgrade project wizard is so very slow every time i upgrade an ASP.NET MVC 4 project. I can see each of the files copied in status bar with a what seems like a forced delay in between each file. The whole process takes more than 10+ minutes and in the meantime the drive activity is very low.
    All other operations with 100 times more files on my SSD machine are very fast and finish in matters of seconds like it is with creating new Kendo UI ASP.NET MVC 4 project.
    Just for the existing project the upgrade operation is very very slow and i wonder if you guys can shed some light on the matter.

    Cheers!
  2. Teodor
    Admin
    Teodor avatar
    56 posts

    Posted 18 May 2013 Link to this post

    Hi Cornel,

    Sorry for the delayed response.

    The file operations are done through the Visual Studio API and it is usually a slow process, especially if you are using TFS/Source Control integration. On my virtual machine it takes a maximum of 1 minute per project - if you have a multitude of projects it can take a significant amount of time. Hope this answers your question.

    Kind regards,
    Teodor
    the Telerik team
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
  3. UI for ASP.NET MVC is VS 2017 Ready
  4. Gene
    Gene avatar
    1 posts
    Member since:
    Jun 2015

    Posted 15 Dec 2015 Link to this post

    I've been waiting for 45 minutes for the upgrade wizard to complete.  I'm assuming it isn't supposed to be that slow to update 2 projects.  I watched the files copy over in the status bar, and now all I see is Telerik VSExtensions: MyProject, Resource (Copy Script Files.)
  5. Ventsi
    Admin
    Ventsi avatar
    46 posts

    Posted 17 Dec 2015 Link to this post

    Hi Gene,

    Thank you for contacting us.

    Indeed, the upgrade of a project takes more time than the creation of new one. Teodor shed some light on the process but here are some more details.

    The upgrade of a project roughly consists of two stages:
    • Copy the new resources in the project directory and add them to the project
    • Remove the old resources from the project and delete them from its directory

    As you know, Kendo contains a lot of script and style files. While the process of copying these files is fast, the process of adding/removing them to/from the project takes more time. To do this the extensions use the Visual Studio API which has its limitations and also does not allow us to have deep control over the process.

    However, 45 minutes is too much time for the upgrade. I would suggest to try the following:

    We are sorry for the inconvenience caused. Please, do not hesitate to contact us in case further questions arise.

    Regards,
    Ventsi
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  6. NerdBrick
    NerdBrick avatar
    25 posts
    Member since:
    Jan 2013

    Posted 06 Jan Link to this post

    I was wondering the same thing about how slow it is to upgrade too.

    We use the _references.js file for helping the JS statement completion. This file dynamically updates as JS files are added to the project. As the KendoUI is updating the JS file, this _references.js file has to be touched to rebuild the JS information. Since there are so many Kendo JS files, it just bogs this process down.

    http://madskristensen.net/post/the-story-behind-_referencesjs 

    To speed things up on our end, we removed the _references.js from the project before running the Kendo update. Then when the update was complete, we added the file back into the project.

    I also think you can turn off the autosync at the top of this file before starting the updates. (There is a right click context menu item to turn it off and on too)

    <autosync enabled="false" />

    Hope this helps. Maybe the Kendo updater can figure out how to turn this file off during update, and refresh it when its done. 

  7. Ventsi
    Admin
    Ventsi avatar
    46 posts

    Posted 08 Jan Link to this post

    Hello Brick,

    Thank you for the detailed idea on how to speed up the upgrade process. We highly appreciate every feedback that would help us improve our products.

    Regards,
    Ventsi
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  8. Stephen
    Stephen avatar
    86 posts
    Member since:
    Jan 2011

    Posted 03 Mar Link to this post

    My upgrade(one kendo project, but multiple projects in solution) has been running almost 3 hours now and it just finished adding the new Content\kendo folder but hasn't yet deleted the old folder. I really don't know what it is doing now.  You can watch the folder on disk as each file is s.l.o.w.l.y. added one by one.

    The Script folder is thankfully done.

    The project *is* connected to TFS which I am willing to blame. "TFS Power Tool Extension" process chugging along.

    i7, 16Gig, SSD, so it isn't a resource issue.

     

  9. Stephen
    Stephen avatar
    86 posts
    Member since:
    Jan 2011

    Posted 03 Mar Link to this post

    So I did some experimenting and maybe it will help others.

     

    I killed my upgrade after 3 hours and refreshed from TFS to get back to clean state.

    _references.js MUST have auto-sync disabled...learned that last upgrade.  You can turn it on again and re-sync after the upgrade is done.

    Then I manually removed the Content\kendo folder from my project.  This took over 10 minutes just for this step.

    I then found this: https://www.cloudconstruct.com/blog/slow-file-management-in-visual-studio-connected-to-team-foundation-services.

    I had 8 workspaces mapped.  I unmapped 5 of them.  I did not restart VS.

    I then manually removed the Scripts\kendo folder from my project.  This took seconds!

    I reverted everything back again and re-ran the kendo upgrade wizard.  This time it finished completely in 15 minutes instead of still running after 3 hours.  Presumably it would have been quicker if I had unmapped all workspaces except my current one.

     

    So, if you use TFS, you MUST turn off _references.js auto-sync and, more importantly, unmap any "unused" TFS workspaces before doing any mass file updates to your solution, either manually or via the kendo upgrade wizard.

     

  10. Ventsi
    Admin
    Ventsi avatar
    46 posts

    Posted 07 Mar Link to this post

    Hi Stephen,

    Thank you for your feedback. I believe many users would find this information and discoveries helpful.

    In addition, the disabling of the _references.js auto-sync is logged in our backlog and will be taken into consideration as soon as possible.

    Your cooperation and willing to help in improving the upgrade process is highly appreciated.

    Regards,
    Ventsi
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  11. Adrian
    Adrian avatar
    2 posts
    Member since:
    Nov 2015

    Posted 16 Jun Link to this post

    The upgrade is still extremely slow.

    I have a Core i7-6700k with 4.4 Mhz, 32 GB RAM, with the project located on a RAMDisk and the Telerik Platform on an SSD, there is no Teamsystem and the upgrade still took over one hour. Only one project had to be updated in my case. 

    Copying the same files by hand takes about 60 seconds, that's over 60 times faster. 

  12. Ventsi
    Admin
    Ventsi avatar
    46 posts

    Posted 17 Jun Link to this post

    Hi Adrian,

    Unfortunately, we still do not have a stable reproduction of this issue.

    In addition, the most time consuming operation is not copying the files, but adding them as part of the solution. As we have mentioned, Visual Studio API has its specifics and limitations which (combined with the high number of files) affects this process and our control over it.

    As a suggestion, did you try the solution that was mentioned in the previous posts - disabling of the _references.js auto-sync before running the upgrade process?

    Regards,
    Ventsi
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  13. Stephen
    Stephen avatar
    86 posts
    Member since:
    Jan 2011

    Posted 17 Jun in reply to Ventsi Link to this post

    I know this doesn't really help Adrian but I recently did the upgrade to 2016.2.607 and it only took 15-20 minutes as long as I did the _references.js and TFS "tweaks" first.
  14. Alex
    Alex avatar
    19 posts
    Member since:
    Nov 2011

    Posted 29 Jun Link to this post

    Wish I would've found this thread BEFORE I started the upgrade to 2016.2.607... I'm in the middle of it and it's taking forever. 
  15. Stephen
    Stephen avatar
    86 posts
    Member since:
    Jan 2011

    Posted 29 Jun in reply to Alex Link to this post

    You could kill the Visual Studio process in Task Manager, revert the changes from TFS and then re-run after the _references and unmapping tweaks.

    I've killed the process after 3 hours myself.

    Once the upgrade is done, you simply need to remap your folder in TFS and it should pick up all the changes.

     

    You can also monitor how far along the process is using Windows Explorer to look at the Kendo CSS and Script folders to see how many files it has left to copy/remove before deciding whether or not you want to kill it.

  16. Mike
    Mike avatar
    12 posts
    Member since:
    Apr 2013

    Posted 28 Nov Link to this post

    Updating from version 2015.2.902 to 2016.3.1118 using GIT as source control is taking over 90 minutes so far to update one project and the clock is still ticking.
  17. Nikolay Mishev
    Admin
    Nikolay Mishev avatar
    3 posts

    Posted 29 Nov Link to this post

    Hello Mike,

    Thank you for contacting us.

    In the latest version of the UI for ASP.NET MVC VS Extensions  the upgrade time is improved significantly, so I suggest you to upgrade the VS Extensions, you can do that from Visual Studio: Tools->Extensions and Updates->Updates. You can also disable the auto-sync of the _references.js before running the upgrade, as Ventsislav Staykov mentioned before.

    Another thing that will also quicken future upgrades is enabling CDN usage from Configure wizard - Right click on the project->Telerik UI for ASP.NET MVC->Configure project->choose theme(or leave the default)->Next->Check "Use CDN support"->Finish.

    Please let me now if the provided information helps.
     
    Regards,
    Nikolay Mishev
    Telerik by Progress
    Telerik UI for ASP.NET MVC is ready for Visual Studio 2017 RC! Learn more.
Back to Top
UI for ASP.NET MVC is VS 2017 Ready