SLOW rendering on initial load

[dadkind]

Hello All,
We're finishing / tweaking our site but we are having performance issues and need some insight.

If we hit the site, the initial page load can be VERY slow. Subsequent page loads are faster, but still, the initial load time is not acceptable.

I've enabled TRACE on the default.aspx page and see some peculiar output. I'm hoping someone can tell me why we're seeing what we get in the TRACE dump. Specifically what is happening between "ASP.conlib_categorysearchsidebar_ascx (end pre-render)" and the line for "ASP.layouts_adminpanel_ascx (begin pre-render)".

Any insights are appreciated!

-tomas

Code: Select all

Trace Information
Category         Message         From First(s)         From Last(s)
aspx.page         Begin PreInit                  
aspx.page         End PreInit         0.0269185848849069         0.026919
aspx.page         Begin Init         0.0270109818410895         0.000092
aspx.page         End Init         0.0816346639201648         0.054624
aspx.page         Begin InitComplete         0.0816778463292202         0.000043
aspx.page         End InitComplete         0.0816952132872028         0.000017
aspx.page         Begin PreLoad         0.0817085619862808         0.000013
aspx.page         End PreLoad         0.0817285677859328         0.000020
aspx.page         Begin Load         0.0817426444413335         0.000014
aspx.page         End Load         0.0817605393676379         0.000018
aspx.page         Begin LoadComplete         0.0817738085714857         0.000013
aspx.page         End LoadComplete         0.0818097959122453         0.000036
aspx.page         Begin PreRender         0.0818245840249585         0.000015
ASP.conlib_categorysearchsidebar_ascx         Begin PreRender         0.35962229416235         0.277798
ASP.conlib_categorysearchsidebar_ascx         End PreRender         0.359792507949523         0.000170
<<<<<<<<<<< ????????? >>>>>>>>>>>>>>
ASP.layouts_adminpanel_ascx         Begin PreRender         10.4976401445913         10.137848 
ASP.layouts_adminpanel_ascx         End PreRender         10.4976823850569         0.000042
aspx.page         End PreRender         10.4976995470272         0.000017
aspx.page         Begin PreRenderComplete         10.4977152595844         0.000016
aspx.page         End PreRenderComplete         10.4978605268684         0.000145
aspx.page         Begin SaveState         10.5218958382497         0.024035
ViewState Size         1256b         10.5226004899706         0.000705
aspx.page         End SaveState         10.5226299147051         0.000029
aspx.page         Begin SaveStateComplete         10.5226484735916         0.000019
aspx.page         End SaveStateComplete         10.5226728641282         0.000024
aspx.page         Begin Render         10.5226873262604         0.000014
aspx.page         End Render         10.5405559536428         0.017869

[kastnerd]

This is known for ASP.

The server basically goes to sleep. Once you go live, enough hits will prevent it from going to sleep.

[dadkind]

Thanks.

I've seen this before in other sites. But not the level that we're seeing with Able.

I guess what is even more troubling is that subsequent loads still have more of a lag than what would normally be expected, and always at the point after the load process starts, but before my code gets hit. Unfortunately, we don't have the source code option, so there is no way to full trace out the load process.

It's just not the performance we were hoping to get.

-tomas

This is known for ASP.

The server basically goes to sleep. Once you go live, enough hits will prevent it from going to sleep.

[blackstonemedia]

Thanks.

I've seen this before in other sites. But not the level that we're seeing with Able.

I guess what is even more troubling is that subsequent loads still have more of a lag than what would normally be expected, and always at the point after the load process starts, but before my code gets hit. Unfortunately, we don't have the source code option, so there is no way to full trace out the load process.

It's just not the performance we were hoping to get.

-tomas

This is known for ASP.

The server basically goes to sleep. Once you go live, enough hits will prevent it from going to sleep.

Completely agree. Is there a definite resolution to this?

[dadkind]

Completely agree. Is there a definite resolution to this?

We no longer use AbleCommerce.

[blackstonemedia]

Completely agree. Is there a definite resolution to this?

We no longer use AbleCommerce.

What do you use now?

[dadkind]

Completely agree. Is there a definite resolution to this?

We no longer use AbleCommerce.

What do you use now?

We've gone back to ASPDotNetStoreFront.
My client had insisted on AbleCommerce so we rolled out the site using AC.
But in the end we switched things over to ASPDNSF and things seem to work better.
But, your situation may be different.

And for large (enterprise) projects, we use MS Commerce Server. But it has it's own headaches!