Curl Blog : Tags : performance

I went out last night and caught the late showing of The Dark Night. I love that Batmobile, but I can’t imagine driving it to work. I would rather drive Bruce Wayne’s Lamborghini! But even the Lamborghini is not exactly a utilitarian vehicle. I mean I can’t imagine taking my wife and four kids on a camping trip in a Lamborghini. I would rather drive my Chevy Suburban.

The Batmobile, Lamborghini and the Suburban all have strengths and weakness depending on the context in which they are used. The fact is you have to choose the right vehicle for the job at hand. This is also true of RIA platforms.

Let say you have to enrich the user experience of a commercial shopping site like Amazon.com or The Gap. You are probably going to use something fairly lightweight like Ajax. On the other hand, if you want to provide a beautiful animation for Disney you’ll use Flex or Silverlight, not Ajax. Flex might be good for one site and Silverlight another. Ajax framework “X” here and Ajax framework “Y” there. You get the picture.

My platform of choice is Curl, a RIA platform that started as a DARPA funded research project at MIT more than a decade ago. As a RIA platform Curl is very mature and extremely powerful, but it’s not appropriate for all use cases. For example, I wouldn’t build a mass consumer web site with Curl because the Curl runtime is not very common. I would use Ajax or Flex instead. At the same time I wouldn’t build a processing intensive data visualization tool or an advanced product configuration interface (think thousands of parts) using Ajax or Flex either. I would use Curl.

Curl is a powerhouse; it is the Batmobile of the RIA platforms. But its most appropriate for enterprise and scientific computing - its not always the best choice for mass consumer applications. For mass consumer applications I would choose Flex, Silverlight or Ajax - these are the Lamborghinis and Suburbans of the RIA platforms. Flex, Silverlight and Ajax are best suited, in my opinion, for every day use (Suburban) or for glitz and glam (Lamborghini), not for mission critical industrial strength jobs (Batmobile). For mission critical industrial strength jobs that require intensive processing and the ability to handle huge data sets I choose Curl.

When you choose a RIA platform you have to consider many things and in many cases Ajax, Flash/Flex, or Silverlight will do the job nicely. But there are occasions when you need something much more powerful and that’s when you should take a serious look at Curl. Don’t drive the Batmobile to work and don’t drive the Suburban into a battle with evil. Use the right platform for the job.

0 Comments 0 References Permalink Tags: ajax, curl, datavisualization, flex, performance, silverlight

Recently we wrote about some performance measurements showing Curl to be an order of magnitude faster than ActionScript 3 when executing a JPEG encoding algorithm. Our report hit a nerve with Ted Patrick at Adobe, causing him to question

Who cares about JPEG encoding performance in an RIA anyhow? Is there a single mainstream RIA that uses it?
Are the results of any performance benchmark really meaningful? and
Which is more important anyway, performance or wide deployment?

I'd like to address these points. First, JPEG encoding is important in some of Adobe's own applications. The Adobe AIR Salesbuilder application has a feature that can save a snapshot of your dashboard as a JPEG file on your desktop. The Salesbuilder demo script warns that this operation "can take a few seconds." This usability glitch is directly a function of the JPEG encoding speed that we studied. For a more compelling example, consider the recently launched Adobe Photoshop Express service. It can only run in on-line mode, and processing-intensive operations such as JPEG encoding are handled on the server, but if you ever wanted to create an offline, Adobe AIR style of application like this, JPEG encoding speed would absolutely matter. Given the importance of photo sharing and processing in the Web economy, can we really say that this task is not significant?

But for us, JPEG encoding is just a representative of a much larger set of tasks that a truly powerful RIA will have to do, which require application-specific coding in the inner loops. These tasks cannot be structured as just a series of calls from a scripting language to a set of predefined, pre-optimized modules that are bundled into the RIA plugin. For example, a typical requirement for enterprise dashboard applications is to handle a "data cube" model with thousands of data points in it. (See the Curl Business Intelligence Demonstration on our enterprise demos page for one example.) No RIA platform includes data cubes as a primitive data type, so even the inner loops of the code that distills information from the data cube to the presentation have to be written as part of the RIA application, where they are subject to the same performance laws as our JPEG encoding case study.

Regarding question (2), we think our benchmark test was pretty fair because we just used the same coding structure that is used in Adobe's own code. However, we would welcome any interest from Adobe in improving their ActionScript for JPEG encoding and reporting on the results!

Finally, the value of wide deployment over performance varies a lot depending on your situation. In many scenarios, wide deployment is very important. Heck, we use Flash ourselves to add some visual punch to our corporate home page that all comers can enjoy! For this kind of application, wide deployment often trumps performance and you adjust your ambitions, if necessary, to fit the constraints of the platform.

But Curl has excelled for enterprise applications and is already in use by more than 300 companies, many of them household names, for mission-critical applications. These applications aren't too visible because most of them exist entirely behind corporate firewalls, but they testify that Curl is in fact a trustworthy, industrial-strength platform. For this type of customer, breadth of deployment on the Internet is absolutely not the issue; the capability of the platform to host powerful, responsive applications is.