Skip to main content

So you have your website deployed in PROD ... now what ??

Posting on behalf of Usr.Web.Speed -

My previous job had been to architect and develop websites for various customers. During that time my team and I have architected and developed various web applications mainly for enterprises. (But below info is not restricted to enterprises)

Other than the usual development and testing tasks involved, our focus area was to abide by multiple SLAs. One of the primary SLAs was to provide the users of our websites a very low (usually subsecond) response time (or page load time).

To adhere to this SLA, we did multiple activities, in code, process as well as infrastructure. These include (but not limit to) -

  • Using best practices including (http://developer.yahoo.com/performance/rules.html)
  • Determining the optimum number of calls to the databases, open connections, etc.
  • Providing the fastest mechanisms to download associated content (such as stylesheets, JS files, etc. over CDN)
  • And debugging the reason for the slowness of the websites, when we find any.

After the development is complete, but before deploying it to PROD (production environment), we deployed code to a sanitized PROD-like environment. And load tests were executed using tools (such as - Visual Studio load test or ApacheBench). 

Once the tests are executed, it was then deployed to PROD.
But the question we always had was "is this enough". What we realized was that we do not have any mechanisms to continue monitoring the speed of the web pages after deployment.

The reasons for continuing monitoring is many including -

  • We executed the load tests making certain assumptions (how users use the application, that all users are the same, and there are no other problems) - but in practice, we know that most of these assumptions are theoretical. 
  • The web pages load up other dependent resources from other servers, (not under your control) - when was the last time you added a FB like button on your page? - and do they have an SLA ?

How Usr.Web.Speed. can help you - 

When you sign-up for Usr.Web.Speed, we provide you a one-liner JavaScript code snippet. This snippet should be added to the HEAD tag of your website.
Once this is done, the script will automatically log the speeds of your pages as and when users open your website. 
Also captured is data on how much time it takes to download and load the dependent 
  • JS files 
  • CSS files
  • Images
  • your AJAX calls
Once captured, Usr.Web.Speed processes these logs and provides your insights to the speed of the performance of your application via a dashboard and graphs. 

And the best part of all this - it is FREE during the beta period. So what are you waiting for ? SIGN UP, now.

And remember - do provide some feedback or new feature requests


Comments

Popular posts from this blog

The fight is in the open

Been busy lately and so have not managed to post for quite long. But I just had to post this. This post is dedicated to all persons who dont know anything about the fight between MS and Google: Check out the links starting from: http://news.zdnet.com/2100-9588_22-5875433.html?tag=nl.e589 There are more links as you get thru the article. Be sure to read those too. And just as a side-note: Check out " Atlas ". These are client side and server side components, which easily (??) enable you to make Web calls. This is done by encapsulating AJAX. (please dont insult by telling me that you dont know what that is).

Finally decided

I have been having these various itch since quite some time. Both about what i am doing here (where i work) and what am i meant to do. Finally, i have decided "I need a job change". I guess IT services industry was never meant to be the right industry for me. Don't get me wrong there, it's not that i wanna quit because i am not getting any interesting work, it's just that I have ideas about life which does not match with what my company is doing. (As amatter of fact, they have some really beautiful concepts which are great to work on). But i have believed web to be the future and now i have started realising that personal dreams do become quite a pain in the neck, when they are ignoired. Huh.... now that i put it on a log, i feel much better. Back to work...

News Feature

Enough of idle minds' posts. Instead got down to the engines of coding and coded the "Top News Stories", available on the right :D, on the side bar. Initially on load of the page, i was planning to show all the current top stories, accessing it from other sites. But, IE seems to have some security restrictions on a web page accessing resources of other web sites. Ok, i think that's what it is. So it pops up some security message. So i have shifted over to using a textbox and a "Go" button. On the click of the "Go" all the news as per the xml feed in the text box will be displayed. Go ahead and try it, but remember to click "Yes" on the security warning. Anyway for the knowledgeable. On click of the "Go!!!" it uses XmlHttpRequest , retrieves the XML feed from the site mentioned in the text box and displays it in "user friendly" format.