OData-related performance issue












0















I'm having issues with really long response times in a Web API/OData scenario.
I have an ASP.NET Core Web API which in turn calls an ASP.NET Core OData API. Excerpt form logs:




Issuing Odata request at: 01.34.58.088596

Odata controller get at: 01.34.59.414334 Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request
finished in 4519.7697ms

OData response received at 01.49.12.56983
Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request
finished in 15042.4031ms




Some obeservations:




  • It takes ~1.5 seconds for the OData request to reach the OData controller.

  • The OData request takes 4.5 seconds. In the request an EF query is performed, which takes about 0.5 seconds when run on its own.
    Where is the remaining ~4 seconds spent?

  • OData response is received after ~15s. Take away the 4.5 seconds for the OData request, where is the remaining 10.5 seconds spent?


Everything is latest version and running in IIS express.



Any input appreciated.










share|improve this question



























    0















    I'm having issues with really long response times in a Web API/OData scenario.
    I have an ASP.NET Core Web API which in turn calls an ASP.NET Core OData API. Excerpt form logs:




    Issuing Odata request at: 01.34.58.088596

    Odata controller get at: 01.34.59.414334 Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request
    finished in 4519.7697ms

    OData response received at 01.49.12.56983
    Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request
    finished in 15042.4031ms




    Some obeservations:




    • It takes ~1.5 seconds for the OData request to reach the OData controller.

    • The OData request takes 4.5 seconds. In the request an EF query is performed, which takes about 0.5 seconds when run on its own.
      Where is the remaining ~4 seconds spent?

    • OData response is received after ~15s. Take away the 4.5 seconds for the OData request, where is the remaining 10.5 seconds spent?


    Everything is latest version and running in IIS express.



    Any input appreciated.










    share|improve this question

























      0












      0








      0








      I'm having issues with really long response times in a Web API/OData scenario.
      I have an ASP.NET Core Web API which in turn calls an ASP.NET Core OData API. Excerpt form logs:




      Issuing Odata request at: 01.34.58.088596

      Odata controller get at: 01.34.59.414334 Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request
      finished in 4519.7697ms

      OData response received at 01.49.12.56983
      Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request
      finished in 15042.4031ms




      Some obeservations:




      • It takes ~1.5 seconds for the OData request to reach the OData controller.

      • The OData request takes 4.5 seconds. In the request an EF query is performed, which takes about 0.5 seconds when run on its own.
        Where is the remaining ~4 seconds spent?

      • OData response is received after ~15s. Take away the 4.5 seconds for the OData request, where is the remaining 10.5 seconds spent?


      Everything is latest version and running in IIS express.



      Any input appreciated.










      share|improve this question














      I'm having issues with really long response times in a Web API/OData scenario.
      I have an ASP.NET Core Web API which in turn calls an ASP.NET Core OData API. Excerpt form logs:




      Issuing Odata request at: 01.34.58.088596

      Odata controller get at: 01.34.59.414334 Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request
      finished in 4519.7697ms

      OData response received at 01.49.12.56983
      Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request
      finished in 15042.4031ms




      Some obeservations:




      • It takes ~1.5 seconds for the OData request to reach the OData controller.

      • The OData request takes 4.5 seconds. In the request an EF query is performed, which takes about 0.5 seconds when run on its own.
        Where is the remaining ~4 seconds spent?

      • OData response is received after ~15s. Take away the 4.5 seconds for the OData request, where is the remaining 10.5 seconds spent?


      Everything is latest version and running in IIS express.



      Any input appreciated.







      .net odata asp.net-core-webapi






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 13:07









      RobertRobert

      107311




      107311
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          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%2fstackoverflow.com%2fquestions%2f53412740%2fodata-related-performance-issue%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • 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%2fstackoverflow.com%2fquestions%2f53412740%2fodata-related-performance-issue%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

          MongoDB - Not Authorized To Execute Command

          How to fix TextFormField cause rebuild widget in Flutter

          in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith