Earlier quoted context omitted.
We started out with mondrian+mysql, but quickly had to drop mysql ("mysql is great until you want to put data into it and then get it back out again" - unattributed, to protect the guilty). Our primary work was with postgresql in the beginning. which, in my opinion, is a pretty solid database to work with overall. We did partition all of our dimension and facts tables, which helped a great deal. Aggregates were a pro…
With all due respect to pgsql, mondiran and mysql - you're using the wrong toolkit. You need a column store, like Vertica, kdb+, TimesTen (now Oracle?), Sybase anytime (I think that was what it was called). You can do very well at much, much lower cost in the Python world: pandas, PyTables, or even just straight numpy. Seriously, using any of these would make the report generation time basically zero, and you'd just…
We ended up with a golang solution that we use essentially like you would with a column store. It's very fast and extremely thin.