A busy break from blogging

Between July 17th and August 22nd, I saw 57 movies and read 7 books. There were Saturdays when I watched four movies back-to-back. (I tried five. Couldn’t stay awake.) Amidst this, I also cooked, cleaned, shopped… and went to office. (Oh yes, I was working 10 hours a day.) And managed to build some interesting sites which I’ll release in a while.

But first, let me share the books with you.

Harry Potter and the Deathly Hallows

I wasn’t planning to buy it. I figured I’d just wait for the soft copy. On 21st July at 8am, I went shopping to the local Sainsbury’s to get groceries for my pre-movie cooking. I didn’t know that was the release date. And there it was. In a huge stack. 50% discount. Should I? Shouldn’t I? After finishing the rest of my shopping, and having deeply analysed the cost-benefit and ROI, I figured: if I didn’t buy it now, someone else might tell me the answers!

Was Snape evil? I couldn’t believe that. Not after Dumbledore’s implicit trust. Besides, I re-read Harry Potter and the Half-Blood Prince, and if Dumbledore was dismissing Harry’s explicit warnings about Snape, he had to know something more. Anyway, what was the significance of Dumbledore’s last words? "Severus… please…" Please what? Dumbledore begging for death seemed more likely than Dumbledore begging for life. I had to know.

Who dies? Voldemort, of course. But who else? It couldn’t be Harry, unless J K Rowling was looking to make herself one of the most hated novelists. Yet, it seems so… possible. Harry dying to take Voldemort out. Naah, can’t be. Not Ron or Hermione either. Same reason. One of the other Weasleys? Maybe. Plenty of them anyway. Hopefully Percy. Hargrid? Possible. Lupin? The last of Harry’s father’s friends?

And all the minor questions: What’s the significance of Harry’s eyes? What does Wormtail do to help Harry? What’s the significance of Voldemort having used Harry’s blood to resurrect himself? etc. etc.

So I bought it.

But didn’t start reading.

I knew that if I picked it up, I wouldn’t put it down. It was time to cook. And watch movies.

By 4:00pm, after three movies, I couldn’t stand it any more. So I picked it up. Read until 2:00am. Picked it up again on Sunday at 9:00am, and starved until 11:00am until I finished it.

Whew! What a book. Definitely the raciest of the lot. My earlier favourite in the series was The Prisoner of Azkaban, though The Half-Blood Prince came close. But this one beats them all. Resolves most of the mysteries till date, too. As Stephen King says in his review of Harry Potter, but by the time she penned the final line of Deathly Hallows, she had become one of the finer stylists in her native country.

How to be Good

And then there was Nick Hornby’s book. I’d seen a couple of his movies: About a Boy and High Fidelity. They were interesting, and I’d heard the books were good. Figured I’d pick one up.

And it was hilarious!

How to be Good is the funniest book I’ve read since Five Point Someone and The Inscrutable Americans. Most of my colleagues kept wondering what I was laughing out so loudly about.

This is the story. The author is a doctor and a good wife. “Gooder” than her husband, certainly, and that makes her feel good. Until he has suddently becomes GOOD. Truly good. Saint-like. And then she can’t stand him any more. The story is in first person, so you can see her thoughts almost verbatim. (See thoughts verbatim? Well, whatever the phrase is.)

The Runaway Jury

I had just seen the movie Runaway Jury, so I had to re-read it immediately. The movie was surprisingly good, though. Dustin Hoffman, Gene Hackman, John Cusack and Rachel Weisz. Many changes from the book, but didn’t detract from the experience.

Batman Year One, The Dark Knight Returns and Understanding Comics

I saw 300. WOW! Brilliant. One of the greatest visual experiences ever. Possibly better than V for Vendetta and certainly better than Sin City — both of which I thought had incredible visuals. The colours, the texture, the contrast, the surrealism — whew!

That’s when it hit me. Three of the best movies I’ve seen recently were based on graphic novels (comics). Two by Frank Miller. Maybe I should explore this a little more.

I got myself Batman Year One — and that’s when I realised where Batman Begins got its inspiration from. The graphics were pretty old style, but the story, incredible. Then I picked up The Dark Knight Returns. Now THAT is phenomenal graphics. And what a story! Christopher Nolan‘s next movie is slated to be The Dark Knight. Really looking forward to that.

With all this, I ended up reading a bunch of new Superman comics as well (but they were lousy, so I won’t mention anything), and in the meanwhile, heard about Scott McCloud‘s comic book on comics — Understanding Comics. Like I said, it’s a comic book, but non-fiction. It’s about the history and art of comics. Very nice reading, and quite insightful too. I think every visual designer should take a look at it.

Pro Javascript Techniques

I’d been reading up a lot of Javascript recently — learning mostly from Douglas Crockford, Peter Paul-Koch, Dean Edwards, and John Resig. So when I realised John had a book, I had to read it. Douglas Crockford recommends JavaScript: The Definitive Guide (5th Edition) as the least bad among many bad books. I read it. Sorry, but it was quite a bore. Pro Javascript Techniques on the other hand, is gripping. Dives right into modern techniques, writing style, and is filled with practical advice. How wonderful.


So anyway, that’s what my month’s been like. Well worth the break from blogging, I think. (And I haven’t even told you about the movies or sites yet! Well, soon.)

Default camera ISO setting

In those early days, when all I had was an analog SLR, I had to make choices up-front. Do I buy an ISO 100 film for daytime shooting? (It’s cheaper, besides.) Do I go in for the expensive ISO 1600 film for my fancy night shots? Do I lug around the tripod? Do I use the flash? Do I even bother taking indoor shots? etc.

With my new digital camera, at least the ISO choice vanishes. The ISO range varies from 64 to 1600. And so, I don’t need flash or a tripod most of the time.

But once in a while, I get into a tricky situation.

Having a digital camera lets me take pictures a lot faster. Suppose I spot a boat speeding by when strolling along the Thames. The time it takes from the instant I see it to the instant I click the shutter is about 5 seconds. 2 seconds to pull out the camera, 1.5 seconds for the camera to start up, and about 1.5 seconds for me to aim and shoot.

I love being able to do this kind of a thing.

Except, it’s still a bit tricky managing the ISO. It takes me about 10 seconds to change the ISO settings. No, not because the menus are complex… that accounts for only about 3 seconds or so. The bulk of it is because I have to think about what ISO setting to use — especially given that I like to overexpose digital camera images a bit.

So, when I’m going indoors, I have to remember to set the ISO to something like 400 or 800, and back again when I get out. It may sound like I’m going a too far, but the thing is, since I don’t keep my tripod always attached, and don’t ever turn on the flash, I’ve spoiled a fair number of impulsive indoor and night shots because I’ve had the wrong ISO setting at the wrong time.

Being digital images, many of these problems can be fixed.

If I use a high ISO setting (say ISO 800), I get a fair bit of digital noise. But NeatImage does a decent job of reducing noise (thanks, Dhar!), so the result is not too bad.

If I use a low ISO setting (say ISO 100), I get clean images in bright light, but blurred images in low light (no tripod, no flash, you see). I haven’t found anything that can recover from a blurred image.

I decided, on the balance, to have a slightly higher ISO setting by default. I get slightly noisier images, but that’s less of a worry.

So I leave the camera in ISO 400. I can quickly shoot indoors. If I have the time and need, I shift to ISO 100, or use a tripod if required. Then I set it back to ISO 400 when done.

Tamil songs quiz 2006-2007

Here is the background music from some hit songs from 2006 and 2007. Can you guess which movie they are from?

Don’t worry about the spelling. Just spell it like it sounds, and the box will turn green. (A couple of spellings are tricky. Try J instead of S and V instead of G.)

Search for the song and listen online, if you want to confirm your guess.

Score: 0 / 10
Song 1
Song 2
Song 3
Song 4
Song 5
Song 6
Song 7
Song 8
Song 9
Song 10

Making my music search engine faster

My music search engine takes quite a while to load (typically 40 seconds). That’s an unusually long time for a page, given that most of the people that access it are on broadband connections, and are listening to music online.

The reason is, firstly, that I’m loading a lot of data. Literally every single song on that you can search comes through as Javascript. All the downloadable Hindi songs, for instance, occupy 1.3 megabytes before compression. On average, this takes about 20 seconds to load.

The second reason is, I’m doing a lot of processing with the data. Two things take the bulk of the time: uncompressing the data, and massaging it to allow for different spellings. On average, that takes about 20 seconds.

40 seconds is too long to wait. Actually, the perceived waiting time is 8 seconds, because I start showing the search and the results after 1/5th of the data is downloaded. But 8 seconds is still too long.

I managed to cut this time by half with two things I just learned.

Firstly, Javascript loads and executes sequentially. As soon as a Javascript block is loaded, it is executed. While it is being executed, the rest of the HTML file is not parsed. So any subsequent Javascript blocks (or images, CSS, any other external links) are not loaded. Bandwidth is just sitting idle while the browser is busy at work on the Javascript.

Since I’ve split all my songs into five equal-sized Javascript files, my search engine loads the Javascript files one after another! The problem is even worse — the calculations I do in Javascript take up as much time as the load time. If the loading went on in parallel, by the time the first calculation is done, the second script would have loaded.

This problem can be solved for Internet Explorer and Opera. The “defer” attribute loads the scripts in the background, and defers their execution. This reduces the loading time to nearly zero for all the Javascript files except for the first one or two, because by the time my calculations are done, the next script is already loaded.

Javascript loading sequence before and after 'defer'

These Javascript files contain a list of songs as a long string, which I then split into individual songs. Then I modify each song using regular expressions so that approximate matches will still work. (For e.g., typing “aa” is the same as typing “a” on this search engine.) The performance of regular expressions is critical to me.

Originally, I did this:

  1. Split the string into songs
  2. Modify each song using regular expressions

Now, I changed the sequence to this:

  1. Modify the string using regular expressions
  2. Split the string into songs

When I timed the speed of this change, I realised browsers differ a lot in the speed of processing regular expressions. Here is the time (in seconds) for each browser to process the Javascript before and after the change.

Browser Before After
Internet Explorer 6.3 5.0
Firefox 17.7 4.7
Opera 93.8 19.9

Internet Explorer wasn’t affected much by this change. But Firefox and Opera were heavily impacted. I’m guessing this is because Firefox and Opera have a high setup time for matching regular expressions. Before, I was matching thousands of strings. After, I was matching only one (long) string. IE didn’t care much. Firefox and Opera speeded up dramatically. (I suspect my Opera data is skewed by a few people using a rather slow machine… but then, that’s probably why they should use Opera in the first place — it works rather well old machines.)

With these changes, my total load time fell from about 40 seconds to about 20 seconds. Pretty decent improvement.

There are two further steps I could take from here on.

Compress the songs files further

Currently, I’m doing two things to compress the songs.

  1. Instead of sending the list as a (movie-song),(movie-song),... combination for every song, I send it as a (movie-song,song,song,...)(movie-song,song,song,...)... combination. So I don’t repeat the movie names.
  2. Secondly, I compress them via HTTP/1.1. (My server doesn’t let me do that with Javascript, actually, because Netscape 4.x doesn’t accept compressed Javascript. But since it’s such an old browser and none of my viewers use it, I trick the server by renaming my Javascript files as .html, and it passes them on compressed.

What I could do additionally is:

  1. Remove duplicate songs. If songs are spelt differently, I include them both. But I can knock off the duplicate ones.
  2. Compress the text. Though I’m gzipping the text before sending it, I suspect there may be ways of storing the data in a more compressed form. For example, many songs are repeated with the (male) and (female) versions. These could be clubbed (somehow…)

Speed up the Javascript calculations further

There are two steps I’m doing right now:

  1. Modify the string using regular expressions
  2. Split the string into songs

Here’s how much time each step takes (in seconds) across browsers. (Note: these were based on one day’s data, sampling about 2,000 page views)

Browser Regular expression Split
Internet Explorer 0.88 3.04
Firefox 3.76 1.08
Safari 0.47 0.46
Opera 4.96 29.78

Firefox takes a lot of time with regular expressions. IE and Opera take a lot longer to split (which involves creating many objects). I may have to think up different optimisations for the two.

The code is available in the HTML of the song search engine. It’s readable. The stuff I’m talking about is in the function sl(p,s). Any thoughts are welcome!

Reducing the server load

I’m been using a shared hosting service with 100 WebSpace over the last 7 years. It’s an ad-free account that offers 100MB of space and 3GB of bandwidth per month. Things were fine until two months ago, which was when my song search engines started attracting an audience. I had anticipated that I might run out of bandwidth, so I used a different server (that has 5GB of bandwidth per month quota) for loading the songs. But what I didn’t anticipate whas that my server load would run over the allotted CPU limit.

You’d think this is unusual, given how cheap computing power is, and that I’d run out of bandwidth quicker. But no. My allotted limit was 1.3% of CPU usage (whatever that meant), and about 2 months ago, I hit 1.5% a few times. I upgraded my account to one which had a 2.5% limit immediately, but the question was: why did this happen?

This blog uses a lot of Perl scripts. I store all articles on a MySQL database. Every time a link is requested, I dynamically generate the HTML by pulling up the article from the MySQL database and formatting the text based on a template.

Schematic of how my website displays pages

I also use MySQL to store users’ comments. Every time I display each page, I also pull out the comments related to that page.

I can’t store the files directly as HTML because I keep changing the template. Every time I change the template, I have to regenerate all the files. If I do that on my laptop and upload it, I consume a lot of bandwidth. If I do that on the server, I consume a lot of server CPU time.

Anyway, since I’d upgraded my account, I thought things would be fine. Two weeks ago, I hit the 2.5% limit as well. No choice. Had to do something.

If you read the O’Reilly Radar Database War Stories, you’ll gather that databases are great for queries, joins and the like, while flat files are better to process large volume data as a batch. Since page requests come one by one, and I don’t need to do much batch processing, I’d gone in for a MySQL design. But there’s a fair bit of overhead to each databasse query, and that’s the key problem. Perl takes a while to load (and I suspect my server is not using mod_perl). The DBI module takes a while to load. Connecting to MySQL takes a while. (The query itself, though, is quite fast.)

So I moved to flat files instead. Instead of looking up from a database, I just look up a test file using grep. (I don’t use Perl’s regular expression matching because regular expression matching in UNIX is faster than in Perl.) I have a 1.6MB text file that contains all my blog entries.

But looking up a 1.6MB text file takes a while. So I split the file based on the first letter of the title. So this post (Reducing the server load) would go under a file x.r.txt (for ‘R’) while my last post (Calvin and Hobbes animated) would go under a file x.c.txt (for ‘C’). This speeds up the grep by a factor of 5-10.

On average, using MySQL query used to take 0.9 seconds per query. Now, using grep, it’s down to about 0.5 seconds per query. Flat files reduced the CPU load by about half. (And as a bonus, my site has no SQL code. I never did like SQL that much.)

So that’s why you haven’t seen any posts from me the last couple of weeks. Partly because I didn’t have anything to say. Partly because I was forced to revamp this site.

Calvin and Hobbes animated

A Calvin and Hobbes cartoon, drawn by Dadomani.

Dilbert Browser

Al Donovan has created a Dilbert repository by crawling United Media’s site every day since 1996. I’ve made them a little easier to navigate. Click here to see the Dilbert Browser. Use the left and right arrow keys to see the next comic.

Calvin and Hobbes Tracer Bullet 1

My all-time favourite series from Calvin and Hobbes.

QUIZ: Jack and Joe leave their homes at the same time and drive towards each other. Jack drives at 60 mph, while Joe drives at 30 mph. They pass each other in 10 minutes. How far apart were Jack and Joe when they started? It was another baffling case. But then, you don't hire a private eye for the easy ones ...

I'd planned to take the day off and spend time with a couple of buddies. My buddies travel light and they're fun to have around. One travels in a holster, and the other in a hip flask. My name is Bullet. Tracer Bullet. What people call me is something else again. I'm a private eye. It says so on my door. The last thing I wanted this morning was a case to solve, but the dame who brought it was persuasive. Most dames are, somehow. Get to work, Calvin. I told her it would cost fifty greenbacks a day, plus expenses.

I stepped out into the rainy streets and reviewed the facts. There weren't many. Two saps, Jack and Joe, drive towards each other at 60 and 30 mph. After 10 minutes, they pass. I'm supposed to find out how far apart they started. Questions pour down like the rain. Who ARE these mugs? What were they trying to accomplish? Why was Jack in such a hurry? And what difference does it make where they started from? I had a hunch that, before this was over, I'd be sorry I asked.

First I figured I'd try the Derkins dame. Susie and I never hit it off, although occasionally we hit each other. Susie had a face that suggested somebody upstairs had a weird sense of humor, but I wasn't going to her place for laughs. I needed information. The way I looked at it, Derkins acted awfully smug for a dame who had a head for numbers and not much else. Maybe she's got something on Jack and Joe. The question is, will she sing? No, I won't tell you what the answer is. Do your OWN work!

The Derkins dame wasn't talking. Someone had gotten to her first and shut her up good. I knew Susie, and closing her mouth would've taken some work. I needed a clue and a drink. One of them I knew where to find. You've made enough trips to the water fountain. Finish your quiz. Suddenly a gorilla pulled me in an alley, squeezed my spine into an accordion, and played a polka on me with brass knuckles. Youse ain't going nowhere, flatfoot.

The inside of my head was exploding with fireworks. Fortunately, my last thought turned out the lights when it left. When I came to, the pieces all fit together. Jack and Joe's lives were defined by integers. Obviously, they were part of a 'numbers' racket! Back in the office, I pulled the files on all the numbers BIG enough to keep Susie quiet and want me out of the picture. The answer hit me like a .44 slug. It had to be the number they called 'Mr. Billion'. Answer: 1,000,000,000. Case closed! Time's up. Bring your papers forward. What did you get, Calvin? I think the answer's 15.

Calvin and Hobbes Dad explains science

My second most favourite series from Calvin and Hobbes, where Dad teaches Calvin the wonders of science.

How do they know the load limit on bridges Dad? They drive bigger and bigger trucks over the bridge until it breaks. Then they weigh the last truck and rebuild the bridge. Oh. I should've guessed. Dear, if you don't know the answer. Just tell him!

Why does the sky turn red as the sun sets? That's all the oxygen in the atmosphere catching fire. Where does the sun go when it sets? The sun sets in the west. In Arizona actually, near flagstaff. Oh. That's why the rocks there are so red. Don't the people get burned up? No, the sun goes out as it sets. That's why it's dark at night. Doesn't the sun crush the whole state when it lands? Ha ha, of course not. Hold a quarter up. See, the sun's just about the same size. I thought I read that the sun was really big. You can't believe everything you read, I'm afraid. So how does the sun rise in the east if it lands in Arizona each night? Well, time for bed. I hope someday I'm as smart as Dad is. Why, what did he tell you now?

Dad, will you explain the theory of relativity to me? I don't understand why time goes slower at great speed. It's because you keep changing time zones. See, if you fly to California, you gain three hours on a five-hour flight, right? So if you go at the speed of light, you gain MORE time, because it doesn't take as long to get there. Of course, the theory of relativity works only if you're going west. Gee, that's not what Mom said at ALL! She must be totally off her rocker. Well, we men are better at abstract reasoning. Go tell her that.

How do bank machines work, Dad? Well, let's say you wwant 25 dollars. You punch in the amount... and behind the machine, there's a guy with a printing press who makes the money and sticks it out this slot. Sort of like the huy who lives up in our garage and opens the door? Exactly.

Why does ice float? Because it's cold. Ice wants to get warm, so it goes on top of liquids in order to be nearer to the sun. Is that true? Look it up and find out. I should just look stuff up in the first place. You can learn a lot, talking to me.

Wow, honey, you're missing a beautiful sunset out here. I'll count to 10, and then... POW! Dad, how come old photographs are always black and white? Didn't they have color film back then? Sure they did. In fact, those old photographs ARE in color. It's just that the WORLD was black and white then. Really? Yep. The world didn't turn color until sometime in the 1930s, and it was pretty grainy color for a while, too. That's really weird. Well, truth is stranger than fiction. But then why are old PAINTINGS in color?! If the world was black and white, wouldn't artists have painted it that way? Not necessarily. A lot of great artists were insane. But... but how could they have painted in color anyway? Wouldn't their paints have been shades of gray back then? Of course, but they turned colors like everything else did in the '30s. So why didn't old black and white photos turn color too? Because they were color pictures of black and white, remember? The world is a complicated place, Hobbes. Whenever it seems that way, I take a nap in a tree and wait for dinner.

Web lookup using Excel

Take a look at the Excel screenshot below.

Amazon Web Prices

Yes, that’s right. I have a user-defined function called AMAZONPRICE. And it returns these cameras’ prices directly from Amazon.com. (Given the category and some keywords, it returns the price of the bestselling item on Amazon.com.)

Here’s the code behind the function.

Function AmazonPrice(index As String, keywords As String) As String
  Dim xDoc As MSXML2.DOMDocument30
  Set xDoc = New MSXML2.DOMDocument30
  xDoc.async = False
  If xDoc.Load("http://ecs.amazonaws.com/onca/xml?Service=AWSECommerceService" _
    "&Version=2005-03-23&Operation=ItemSearch&SubscriptionId=03SDGQDFEB455W53SB82" _
    "&AssociateTag=sanand-20&MinimumPrice=10000&ResponseGroup=OfferSummary,Small" _
    "&Sort=salesrank&SearchIndex=" & index & "&Keywords=" & keywords) Then
    xDoc.setProperty "SelectionLanguage", "XPath"
    xDoc.setProperty "SelectionNamespaces", _
      "xmlns:a=""http://webservices.amazon.com/AWSECommerceService/2005-03-23"""
    AmazonPrice = xDoc.selectSingleNode("/a:ItemSearchResponse//a:Amount").Text
  End If
End Function

This is how it all started…

Flickr has a camera finder that shows the most popular cameras in the Flickr community.

Flickr Camera Finder

I love comparing gadgets, I’d been doing some research around these cameras, and the Fuji series (because I own a Fuji Finepix S5600). I’d normally make a spreadsheet that compares these cameras on various parameters, including price.

Since I believe in never typing in data, wondered if there was a way to get the prices in automatically…

Two things made this possible.

  1. Amazon offers web services which let you get price (and almost any other) data for their products
  2. Visual Basic lets you use pretty much any ActiveX object as a control. Microsoft offers MSXML which you can use to load (or download) any XML file, and parse it.

The first task is to get the XML feed for a product you want. Amazon lets you do that through by typing in a URL. The best way to construct the URL is through AWSZone. I picked the US ItemSearch method, which searches for a title or keyword within a category, and returns the matches. The feed for the Canon EOS Digital Rebel XT, based on this, would be at:

http://ecs.amazonaws.com/onca/xml?
    Service=AWSECommerceService&
    Version=2005-03-23&
    Operation=ItemSearch&
    SubscriptionId=0525E2PQ81DD7ZTWTK82&
    SearchIndex=Electronics&
    Keywords=Canon EOS Digital Rebel XT&
    Sort=salesrank&
    ResponseGroup=Offers,Small

(You really need to replace the Subscription ID with your own.)

If you retrieved this URL, you have an XML file containing the details of all Canon EOS Digital Rebel XTs, sorted by sales rank.

To load this in Excel, you need to create a UDF in Visual Basic. First, go to Tools – References and enable Microsoft XML, v3.0 or v4.0. Now, to load an XML document, do this:

Dim xDoc As MSXML2.DOMDocument30
Set xDoc = New MSXML2.DOMDocument30
xDoc.async = False
xDoc.Load(url)

If the load succeeds, then you can extract the information fairly easily, using XPath.

xDoc.setProperty "SelectionLanguage", "XPath"
xDoc.setProperty "SelectionNamespaces", _
        "xmlns:a=""http://webservices.amazon.com/AWSECommerceService/2005-03-23"""

The first line says we’ll be searching using XPath. The second line is a workaround to support default namespaces. (Don’t worry about it. I don’t quite get it either.)

Finally, you get the price from the XML tree. In this case, it’s under ItemSearchResponse/Items/Item/OfferSummary/LowestNewPrice/Amount, and it’s in cents.

        AmazonPrice = xDoc.selectSingleNode("/a:ItemSearchResponse//a:Amount").Text

That’s it! Now that this function is defined, just pass it the category and keywords, and you have the price of the first matching product. You can retrieve any other information about products as well — like sales rank, weight, ratings, reviews, etc.


Here’s the spreadsheet for you to play around with.


Excel 2003 Power Programming with VBA (Excel Power Programming With Vba) Writing Excel Macros with VBA, 2nd Edition