There are many online web site monitoring tools that ping your servers from different locations and ensure the servers and net work are performing well.These monitoring solutions have servers all around the world and in many different cities in the U.S.They scan your web site or do a transaction to ensure the site is fully operational and critical functionalities are running fine.
At Pageflakes,we used WebSitePulse (www.websitepulse.com), which was a perfect solution for our needs.We had set up a monitoring system that completes a brand new user visit every five minutes.It called web services with proper parameters and ensures the returned content is valid.This way we can ensure our site is running correctly.We also installed a very expensive web service call in the monitoring system to ensure the site performance is fine.This also gave us an indication whether the site has slowed down or not.
Figure shows the response time of the site for a whole day. You can see that around 2:00 p.m.the site was down because it was timing out.Also,from 11:00 a.m.to 3:00 p.m., there’s high response time, which means the site is getting a big hit.
Web Site Pulse monitors the site response time and shows high response times
All these settings give you valuable indications:
• There might be a job running at 2:00 p.m. that produces a very high response time, possibly a full database backup.
• There is a job running at 11:30 a.m. that is causing a high response time or a traffic surge that is causing a site-wide slowdown.
A detailed view (see Figure )shows the total response time from each test, the number of bytes down loaded,and the number of links checked.This monitor is configured to hit the home page, find all links in it, and hit those links. It basically visits a majority of the site in one visit on every test and ensures the most important pages are functional.
A detailed view shows total response time and details of the check
Testing the individual page performance is important to find resource-hungry pages.Figure shows some slow performing pages.
Hit individual pages and see their response time. This helps diagnose slow loading pages.The most important factor is the First column,which shows time to first byte (TTFB).
The “First” column shows the delay between establishing the connection and getting the first byte of response.The time you see there is the time it takes for the ASP.NET page to execute on the server. So, when you see 3.38 seconds, it means theserver took seconds to execute the page on the server, which is very bad performance.Every hit to this page makes the server have a high CPU and disk I/O; in other words, this page needs to be improved immediately.
By using such monitoring tools, you can keep an eye on your sites 24 × 7 and look in on your site’s performance at different times to see which pages are performing poorly.
ASP.NET Related Interview Questions
|VB.NET Interview Questions||C#. NET Interview Questions|
|ASP.NET Interview Questions||ADO.Net Interview Questions|
|Windows Presentation Foundation(WPF) Interview Questions||Windows CE .NET Interview Questions|
|Dot Net Framework Interview Questions||Asp Dot Net Mvc 4 Interview Questions|
|Asp Dot Net Mvc Interview Questions|
Introducing Web Portals And Dropthings.com
Architecting The Web Portal And Widgets
Building The Web Layer Using Asp.net Ajax
Building The Data And Business Layers Using .net 3.5
Building Client-side Widgets
Optimizing Asp.net Ajax
Creating Asynchronous, Transactional, Cache-friendly Web Services
Improving Server-side Performance And Scalability
Improving Client-side Performance
Solving Common Deployment, Hosting, And Production Challenges
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.