May 24, 2012

Post: Shard-Query turbo charges Infobright community edition (ICE)

improve performance of almost all queries by spreading them over more than one physical server. This is called “scaling out” and it allows Shard-Query to vastly improve

Post: Should we give a MySQL Query Cache a second chance ?

and you’ll see why below. So what I think could be done with MySQL Query Cache so it once again is appealing to improve performancequery depends on. If not you need to re-generate the query result. Removing of stale queries in this case can be done through some sort of

Post: Why MySQL could be slow with large tables ?

in works which would improve performance of index accesses/index scans. For example retrieving index values first and then accessing rows in

Post: Intro to OLAP

to MDX queries and the kind of SQL which a ROLAP tool must generate to answer those queries. Performance challenges with larger databases, and some ways to help performance