Why ReportViewer so slow?

Discussion in 'ASP.NET / ASP.NET Core' started by mezzanine74, May 18, 2011.

  1. Hi,
    I came to last step on deployment of my site to DiscountASP from my current shared hosting (Arvixe).
    I can tell you this hosting works much faster, even on overloaded Gridviews, i am impressed.
    However, i cannot make same comment on ReportViewer performance.

    In my first trial, i failed to run any report (rendered by ReportViewer 8.0). Then some search on google take me to following link by which i added Managed Handler accross IIS Manager and reports are working.

    http://face.edwindeloso.com/deploying-asp-net-reportviewer-problem-in-win-server-2008/2010/08/

    Gridviews are working 4-5 times faster than my current hosting, but ReportViewer working 2-3 times slower here!

    If I compare my settings here to settings in current hosting company, only difference is the Step i followed in above link, adding handler by IIS manager. On my current hosting, i did not need to follow this step, it worked as it is.

    Are you able to run your reports here in good performance?

    Any feedback and support appreceated.
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    That's rather strange..

    Is the grid view / Report viewer making the same query? I want to see where the latency is actually from (DB or the app itself)

    If you don't mind, PM me the URL to the report and Gridview so i can do some testing here.
     
  3. Hi bruce,
    Thanks for your answer.
    I sent a private message to you.
     
  4. Bruce

    Bruce DiscountASP.NET Staff

    Are you using Report Viewer Control remote / local mode? ie. is your webpage connecting to a report hosted on the reporting service server?
     
  5. remote mode.
    Report server and Web server are on different machine.
     
  6. Bruce

    Bruce DiscountASP.NET Staff

    That's the problem.

    I notice your site is hosted in our UK data center, ie. the web server and the database server both located in the UK.

    The problem is that our reporting server is located in the US.

    If you use remote mode, what happen is

    1) your web app makes a call to the reporting server
    2) reporting service connects to the db server from US to UK
    3) reporting service returns the result set back to the web server in UK

    There's 3 round trips across the atlantic.

    I recommend you use Localmode instead.
     

Share This Page