Leveraging footprints on Disk and Memory space between Tableau, Qlikview and Spotfire

Hi guys,

I stumbled upon this great comparison done by Andrei Pandre on DV (Data Visualization tool) footprint on Disk and Memory for 3 In memory BI tools namely Tableau, Qlikview and Spotfire.

Here is an excerpt of the comparison done between the 3 DV tools:

It is interesting to note that for dashboards that has lower Marks or Visible Datapoints as Andrei put it, Tableau's memory footprint is just about 5% off the footprints of both Spotfire and Qlikview, with Qlikview consuming the most memory. This makes sense as when you have lower Visible datapoints in your screen, then logically you shouldn't be consuming more memory. And if you done quite a number of  DV work, you will definitely know that a lot of times more Marks doesn't always mean better dashboards. Sometimes too much data points would just add clutter. As Andrei pointed out, a dashboard with more than a few hundred datapoints is usually a sign of poor design and the designer's lack of understanding of the DV task.

So for people like me who like to tell my stories as simple as possible, and enabling my clients analyze their data with the best experience, Tableau would be the better tool for the job. With its smarter memory management compared with the other two, it gives a good leverage for customers and for me as well as a designer to create DV projects without having too much concern on hardware. In fact a lot of times, people use VM tools to deploy Tableau.

You can see the original articles here:

DV Footprints on Disk and In Memory Part 1

DV Footprints on Disk and In Memory Part 2