Loading a local ASP.NET app takes forever





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I'm working on a large ASP.NET application on my local machine (IIS7, local SQL Server 2014, ASP.NET 4.6.2).



Since a few days, this application usually loads ok (kind of) after a clean/build operation, but starts taking forever (and thus getting frequent timeouts) after a few clicks or after a standard build.



I wasn't able to find what is happening, the CPU is mostly idle, SQL server is reactive (and works ok from SSMS), IIS doesn't have any hanging request except for the current one.



Of course, the same code executed on another computer (same model) with the same configuration (IIS and SQL Server versions, same database) works correctly.



Sorry I don't have any more information to provide, I'm a little clueless here.



Is there some stuff I can check ?



Please ask for more information if needed.










share|improve this question

























  • Have you tried to debug or profile it?

    – user996142
    Apr 27 '18 at 13:43











  • I didn't profile it, but I debug it regularly, but this doesn't help, the behavior is the same. As said, the code is functional, and acceptably efficient on another identical platform.

    – xlecoustillier
    Apr 27 '18 at 13:47











  • Can you debug it on this IIS, pause it, and check thread stacks to find where exactly thread stopped?

    – user996142
    Apr 27 '18 at 14:42











  • It hangs on a huge (and certainly for from optimal) SQL query. What remains to find out is why this query doesn't almays take ages on the same dataset, but I guess I can work from there. Thanks :)

    – xlecoustillier
    May 11 '18 at 8:02


















0















I'm working on a large ASP.NET application on my local machine (IIS7, local SQL Server 2014, ASP.NET 4.6.2).



Since a few days, this application usually loads ok (kind of) after a clean/build operation, but starts taking forever (and thus getting frequent timeouts) after a few clicks or after a standard build.



I wasn't able to find what is happening, the CPU is mostly idle, SQL server is reactive (and works ok from SSMS), IIS doesn't have any hanging request except for the current one.



Of course, the same code executed on another computer (same model) with the same configuration (IIS and SQL Server versions, same database) works correctly.



Sorry I don't have any more information to provide, I'm a little clueless here.



Is there some stuff I can check ?



Please ask for more information if needed.










share|improve this question

























  • Have you tried to debug or profile it?

    – user996142
    Apr 27 '18 at 13:43











  • I didn't profile it, but I debug it regularly, but this doesn't help, the behavior is the same. As said, the code is functional, and acceptably efficient on another identical platform.

    – xlecoustillier
    Apr 27 '18 at 13:47











  • Can you debug it on this IIS, pause it, and check thread stacks to find where exactly thread stopped?

    – user996142
    Apr 27 '18 at 14:42











  • It hangs on a huge (and certainly for from optimal) SQL query. What remains to find out is why this query doesn't almays take ages on the same dataset, but I guess I can work from there. Thanks :)

    – xlecoustillier
    May 11 '18 at 8:02














0












0








0








I'm working on a large ASP.NET application on my local machine (IIS7, local SQL Server 2014, ASP.NET 4.6.2).



Since a few days, this application usually loads ok (kind of) after a clean/build operation, but starts taking forever (and thus getting frequent timeouts) after a few clicks or after a standard build.



I wasn't able to find what is happening, the CPU is mostly idle, SQL server is reactive (and works ok from SSMS), IIS doesn't have any hanging request except for the current one.



Of course, the same code executed on another computer (same model) with the same configuration (IIS and SQL Server versions, same database) works correctly.



Sorry I don't have any more information to provide, I'm a little clueless here.



Is there some stuff I can check ?



Please ask for more information if needed.










share|improve this question
















I'm working on a large ASP.NET application on my local machine (IIS7, local SQL Server 2014, ASP.NET 4.6.2).



Since a few days, this application usually loads ok (kind of) after a clean/build operation, but starts taking forever (and thus getting frequent timeouts) after a few clicks or after a standard build.



I wasn't able to find what is happening, the CPU is mostly idle, SQL server is reactive (and works ok from SSMS), IIS doesn't have any hanging request except for the current one.



Of course, the same code executed on another computer (same model) with the same configuration (IIS and SQL Server versions, same database) works correctly.



Sorry I don't have any more information to provide, I'm a little clueless here.



Is there some stuff I can check ?



Please ask for more information if needed.







sql-server iis asp.net






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 27 '18 at 13:50







xlecoustillier

















asked Apr 27 '18 at 13:38









xlecoustillierxlecoustillier

246411




246411













  • Have you tried to debug or profile it?

    – user996142
    Apr 27 '18 at 13:43











  • I didn't profile it, but I debug it regularly, but this doesn't help, the behavior is the same. As said, the code is functional, and acceptably efficient on another identical platform.

    – xlecoustillier
    Apr 27 '18 at 13:47











  • Can you debug it on this IIS, pause it, and check thread stacks to find where exactly thread stopped?

    – user996142
    Apr 27 '18 at 14:42











  • It hangs on a huge (and certainly for from optimal) SQL query. What remains to find out is why this query doesn't almays take ages on the same dataset, but I guess I can work from there. Thanks :)

    – xlecoustillier
    May 11 '18 at 8:02



















  • Have you tried to debug or profile it?

    – user996142
    Apr 27 '18 at 13:43











  • I didn't profile it, but I debug it regularly, but this doesn't help, the behavior is the same. As said, the code is functional, and acceptably efficient on another identical platform.

    – xlecoustillier
    Apr 27 '18 at 13:47











  • Can you debug it on this IIS, pause it, and check thread stacks to find where exactly thread stopped?

    – user996142
    Apr 27 '18 at 14:42











  • It hangs on a huge (and certainly for from optimal) SQL query. What remains to find out is why this query doesn't almays take ages on the same dataset, but I guess I can work from there. Thanks :)

    – xlecoustillier
    May 11 '18 at 8:02

















Have you tried to debug or profile it?

– user996142
Apr 27 '18 at 13:43





Have you tried to debug or profile it?

– user996142
Apr 27 '18 at 13:43













I didn't profile it, but I debug it regularly, but this doesn't help, the behavior is the same. As said, the code is functional, and acceptably efficient on another identical platform.

– xlecoustillier
Apr 27 '18 at 13:47





I didn't profile it, but I debug it regularly, but this doesn't help, the behavior is the same. As said, the code is functional, and acceptably efficient on another identical platform.

– xlecoustillier
Apr 27 '18 at 13:47













Can you debug it on this IIS, pause it, and check thread stacks to find where exactly thread stopped?

– user996142
Apr 27 '18 at 14:42





Can you debug it on this IIS, pause it, and check thread stacks to find where exactly thread stopped?

– user996142
Apr 27 '18 at 14:42













It hangs on a huge (and certainly for from optimal) SQL query. What remains to find out is why this query doesn't almays take ages on the same dataset, but I guess I can work from there. Thanks :)

– xlecoustillier
May 11 '18 at 8:02





It hangs on a huge (and certainly for from optimal) SQL query. What remains to find out is why this query doesn't almays take ages on the same dataset, but I guess I can work from there. Thanks :)

– xlecoustillier
May 11 '18 at 8:02










1 Answer
1






active

oldest

votes


















-1














when you clean you aplication you also remove cache files, its normal take some time to your application go faster again.
look at you pool on IIS,go on Advanced Configurations > Start Mode : AlwaysRunning






share|improve this answer
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1317721%2floading-a-local-asp-net-app-takes-forever%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    -1














    when you clean you aplication you also remove cache files, its normal take some time to your application go faster again.
    look at you pool on IIS,go on Advanced Configurations > Start Mode : AlwaysRunning






    share|improve this answer




























      -1














      when you clean you aplication you also remove cache files, its normal take some time to your application go faster again.
      look at you pool on IIS,go on Advanced Configurations > Start Mode : AlwaysRunning






      share|improve this answer


























        -1












        -1








        -1







        when you clean you aplication you also remove cache files, its normal take some time to your application go faster again.
        look at you pool on IIS,go on Advanced Configurations > Start Mode : AlwaysRunning






        share|improve this answer













        when you clean you aplication you also remove cache files, its normal take some time to your application go faster again.
        look at you pool on IIS,go on Advanced Configurations > Start Mode : AlwaysRunning







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 5 at 19:19









        MarcosMarcos

        91




        91






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1317721%2floading-a-local-asp-net-app-takes-forever%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Probability when a professor distributes a quiz and homework assignment to a class of n students.

            Aardman Animations

            Are they similar matrix