Skip to main content

BSNL slow (again).

One of my ISPs (the all reliable) BSNL is slow again. This time to non indian servers. All indian servers are fast. The CDN balanced Gmail, Yahoo (and speedtest.net) are pretty fast. Twitter seemed slow. My servers on east cost (USA), aws boxes (east-1), and infoq dowload site are snail paced. This looks something in the lines od UnderWaterSeaCable cut a few days ago.

 

Here is my recorded information from speedtest.net is outlined below.

 

Time IP Download Upload Latency Location Distance
4/26/2010 5:24 PM GMT 117.195.198.xxx 1.19 Mb/s 0.64 Mb/s 128 ms Mumbai 400
4/26/2010 5:44 PM GMT 117.195.198.xxx 1.68 Mb/s 0.71 Mb/s 92 ms New Delhi 800
4/26/2010 5:53 PM GMT 117.195.198.xxx 0.14 Mb/s 0.59 Mb/s 291 ms Bangkok 1500
4/26/2010 5:40 PM GMT 117.195.198.xxx 0.04 Mb/s 0.04 Mb/s 704 ms Riyadh 2100
4/26/2010 5:29 PM GMT 117.195.198.xxx 0.14 Mb/s 0.20 Mb/s 409 ms New York, NY 8050

 

Just shows, how important it is for a Global service to be Highly Available and Location decentralized.

 

Hopefully BSNL gets this resolved soon.

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour...

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value> ...