+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Sitefinity 5.1 - Administration, extremely slow, pages not rendering style

Sitefinity 5.1 - Administration, extremely slow, pages not rendering style

6 posts, 0 answered
  1. Tahir
    Tahir avatar
    16 posts
    Registered:
    02 Jul 2012
    05 Sep 2012
    Link to this post
    Hi,

    As per the title, I am experiencing extremely poor performance on a development laptop running a fresh installation of Sitefinity 5.1.

    The laptop is configured as follows:

    Windows 7 Ultimate X64 (64 bit)
    4GB Ram
    Dual-Core T7800 CPU
    320GB HDD
    MSSQL Server 2008 R2 Developer Edition
    Visual Studio 2010 Premium + MSDN

    I have no problem running other ASP.NET sites, bespoke sites I have built or any 3rd party Web Apps and performance is more than adequate however when trying to run a Sitefinity site locally through IIS (via the Sitefinity Project Manager) the performance is below par.

    When I am able to get to the Dashboard, trying to access the Administration screen is a painful experience, either I will get a timeout or the Administration > Basics screen will load but without any styling whatsoever i.e. it appears broken.

    I have checked the usual places, Task Manager has no indication of any issues, CPU is sitting idle and I can't see any errors in the logs.

    This is becoming a serious hindrance for development as I am unable to develop and test locally before deploying any/all changes the clients server (a hosted account, a Sitefinity recommended partner site).

    The site runs fine on the hosted server however for obvious reasons I don't want to "Trial-an-Error" my development work (in this case I am creating a bespoke theme and constructing the site).

    Any ideas?
  2. Tahir
    Tahir avatar
    16 posts
    Registered:
    02 Jul 2012
    06 Sep 2012
    Link to this post
    Okay this has got pretty bad now.

    I am unable to do ANY development due to this issue and I am now seriously considering telling the client to not go with Sitefinity as a CMS solution.

    I cannot for the life of me get a development setup working.  I have installed the latest version of Sitefinity 5.1, the SDK, Visual Studio 2010 is up to date, Windows 7 is up to date, all the required .NET Runtimes installed and IIS 7.5 is configured correctly (as far as I can tell).
    [rant...]
  3. Tahir
    Tahir avatar
    16 posts
    Registered:
    02 Jul 2012
    07 Sep 2012
    Link to this post
    Always good to have a moan, I may have found the issue, always the bleeding obvious that is missed.

    I recently upgraded my local firewall and AV which I now suspect is causing no end of issues with IIS, disabling the Firewall and AV resolves ALL issues so there is obviously some underlying security issue somewhere with the AV/Firewall (AVG 2012) which is causing the bottlenecks and lag.

    I would recommend anyone who does have similar issues to check this first - as soon as I disabled the firewall and AV, everything was responsive again, in fact performance was great.

    I will investigate this off-topic and find out why AVG is causing an issue.

    Thanks and please excuse the rant!
  4. Andrew
    Andrew avatar
    2 posts
    Registered:
    22 Aug 2012
    12 Sep 2012
    Link to this post
    Hey Tahir,

    Have you had any luck with finding a way to run both AVG and sitefinity 5.1?

    I just updated to 5.1 and have the same issue.


    Thanks,
    Andrew
  5. Andrew
    Andrew avatar
    2 posts
    Registered:
    22 Aug 2012
    12 Sep 2012
    Link to this post
    FYI, updating AVG from 2012 to 2013 fixed the issues I was experiencing with the admin pages timing out.
  6. Tahir
    Tahir avatar
    16 posts
    Registered:
    02 Jul 2012
    28 Sep 2012
    Link to this post
    Hi Andrew,

    It seems to be any calls made by IIS locally to itself are blocked when they appear to be suspicious requests (i.e. made low level by IIS).

    Simplest solution for most firewall apps is to create an inbound and outbound TCP rule for all ports only for the local IP address (in my case it was 127.0.0.1 the system localhost ip address however yours will be specific to your server if its on a network).

    That pretty resolves it however with AVG you need to tell it to specifically allow the worker process to run otherwise it will cause it to die as it tries to block etc.

    Not really AVG's fault or another vendor, but IIS is a common app so maybe some built in rules should be supplied or at least let customers download rules to use.
6 posts, 0 answered