Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Sep 20, 2011 06:08 AM by Bit Blocker
Jan 01, 2010 04:01 PM|LINK
I'm having performance trouble with PWS. My photo pages load quickly, but my home page is very slow. And the
login process is slow as well. All other pages load fast. When I run it
locally all pages run fast. I'm opening, reading and closing some XML files, but I took that code out and tested it remotely and it didn't make a difference Since all the original stuff is Microsoft best practice code I'm thinking is has more
to do with my hosting service. Of course Godaddy says it not them. But, again, when I run it locally and it is super fast and then run it remotely and it takes up to 90 seconds to load the home page, it doesn't seem to be my code that is slowing it down. Should I
just try a different hosting service?
Jan 01, 2010 05:07 PM|LINK
if other pages are working fine, you have to go through your code. If the pages that connect to database are slow, check all the pages that connects to database,... It might be database connectivity issues from the hosting side. In a shared hosting package,
it will be slow...
Jan 03, 2010 10:46 AM|LINK
Are you using a pre-compiled website, or are you using a Web Site Project. If it is the latter, then if your page has not been requested for a long period of time, ASP.Net willl have to re-compile the requested page. I still wouldn't expect this to take
90 seconds, but something to think about. Perhaps try pre-compiling your application and see if that makes any difference.
Jan 04, 2010 12:27 AM|LINK
Not sure what you mean between pre-compiled and Web Site Project. I am familiar with how the server will compile and cache the website, but it happens no matter how many times I request the homepage. Might the server not be caching my website? Or do you
think it is something else?
Jan 05, 2010 05:06 PM|LINK
By pre-compiled, I mean that all of your code is compiled into a DLL (an assembly), and that assembly is what is placed on the web server, along with the aspx pages of your application. If you are uploading the .cs or .vb files, then each time a page is
initially requested, ASP.net takes the code file and compiling it into it's own DLL. As a result, there is a slight delay in the page appearing. Once this is done the first time, it shouldn't need to happen again, until the application pool is recycled,
or something else causes it to be removed.
Are you familiar with the concept of Tracing?
Give the above a try, this will let you see which part of your page it taking a long time to load up.
Hope that helps!
Aug 08, 2010 12:48 AM|LINK
I started to get the same performance issues after i used DataAnnotation and entlib 5 blocks. My application is ASP.Net MVC 2 was hosted on shared hosting plan with Godaddy. I moved the application from Godaddy to another local provider with dedicated server
plan and the problem gone.
Not sure what was the problem but i think it may be related to reflection and shared resources. I was suffering to pass all the security and permission issues of the Medium trusted hosting when deployed the application on Godaddy first time, You should go
to another provider.
Aug 19, 2010 06:47 AM|LINK
I think it must be your network.
I have just tried to open the link, and it worked fine for me :)
Aug 19, 2010 01:58 PM|LINK
IMO, The trouble with the home page is the Photo of the day. There is a point in which you get enough photos in your albums that the "Photo of the day" process takes a lot of time to randomly pick a photo because it searches all photos. I'll have to find
the code, but I fixed the issue by only letting the PHoD code only choose a photo from the last album created. This wasn't perfect, especially if you want to allow any photo on the page, but it met my needs. I don't recall if it was a code, stored procedure
fix, or both. I'll try to find the code, but I haven't used PWS for a few years so I don't know if I still have it.
Set your test code into debug and watch it. When you locate the PHoD code, try changing it to pull only one picture by ID. You will see a huge increase in speed. Once that is verified to be your issue, try changing the code to allow a more random picture
while maintaining speed.
Sep 20, 2011 06:08 AM|LINK
I want to know how to make my website in precomplied format. My website has 40 pages. After creating website on localhost I "build website" from Build menu in visual Studio 2008. Then published website to a folder from Build Menu.
But after publishing website, "bin" folder had only three "dll" files (and i am also using some ads code on pages, so i think these dll concerns with ads code), where as i know and seen somewhere that after publishing website to folder the
"bin" folder contains two different file (dll & complied) for each page. Like if u have home.aspx then "bin" will have "App_Web_home.aspx.b40945e0.dll" and "home.aspx.b40945e0.compiled".
Is there any problem with my compilation or have any other method to make website precomplied??
I am using Asp.net, C#, Visual Studio 2008, Sql server 2005.
Please help me.
Thanking you in advance.