Update on Sun Download Manager 2.0 -- Delivering Results
By Gary Zellerbach on Feb 09, 2007
It's been two months since the release of SDM 2.0, so we took a look at some key statistics to see how it's going. We're very pleased with results so far.
One of the key goals of the project was to improve download completion rates. We know using SDM helps, but not enough customers were using earlier versions because they had to be installed in a separate transaction. By integrating SDM directly into the Sun Download Center (SDLC) download page, we figured more people would use it and completion rates would improve. (Better completion rates are great for our customers and benefit Sun as well.) Happily, we're seeing immediate improvements, as illustrated in this chart comparing completion rates in November, 2006 (before SDM 2) and in December, 2006 (after the release).
I also ran some preliminary numbers for January and found that one of our largest (and most critical) downloads, the 5 segments that make up the Solaris 10 OS DVD images, are running at a greater than 80% completion rate. That's pretty remarkable when you consider it's over 3 gigabytes of content. (When we started obsessing on Solaris completion rates years ago, the files were much smaller yet running at completion rates around 20% -- so you can see why I'm excited by the progress.)
As to increasing adoption of SDM, average download volume for earlier versions was 20-30,000 downloads/month. Since release of SDM 2, we've had 1/2 million downloads!
Another key indicator is customer support issues. Honestly, it was a little scary for us releasing this brand new use of Java Web Start (JaWS) technology -- integrating a JaWS application directly with the download links on SDLC in a highly visible and trafficked environment. But we've only received about 30 support incidents from our customers, which is a great ratio considering the number of downloads and installations. (Some of the support inquiries received were covered in our SDM troubleshooting guide already, but we understand not everyone "reads the manual.")
Finally, a quick Google search didn't find too much chatter about SDM, typically a good thing I guess. "Milek's Blog" had some nice things to say as well as some suggestions for new features -- much appreciated. On the negative side, I found little as well, though there are rare cases where SDM using Java Web Start may not work properly. This is often a case of multiple older Java Runtime Environments on the same system, possibly combined with issues introduced by corporate firewalls and proxies. As we recommend, if possible, uninstall older Java versions and install the latest/greatest. Also, the stand-alone version of SDM is still available and offers a good option when proxy or firewall issues may keep the JaWS version from starting up properly. All in all, considering the volume, these issues are very rare.
So that's a quick summary of results so far. SDM 2.0 is off to a great start and is meeting and exceeding the goals we set for the project. (Now I better get back to work on our current major project -- an all new download system that will replace today's SDLC application. We sincerely hope this project goes at least as well as SDM 2.0!)