The idea of the framework is if you ran a classified ads site, to be able to show your users how many hits their ads receive.
Google doesn't support full HTML. Their problem not mine. If someone wants to port it to wiki markup I'd give you 100 thank yous.
The example:
LOG TABLE
'firefox', '127.0.0.1', '800x600'
'IE', '127.0.0.2', '1024x769'
(imagine the log table went on for a billion more rows)
Much more efficient to store something like this:
Month,day,year,screen_rez,count
'Feb', '1', '2009', '800x600', '52'
Instead of storing 52 individual rows, we store 1 single row that describes that "segment" of our traffic. This is called a rollup.
Lots of tool vendors offer rollups (oracle) but seeing as those are not open source and my solution IS, I think there is a reason for it to exist

Plus a corp. just licensed (hired me to implement it on their site) which more than payed for the time its taken to create
So heres how I'd sum it up in 1 sentence.
Instead of running a COUNT query on a billion rows, its more efficient to run a SUM query on a million rows that each contain the VALUE "1,000".
I am still researching an anomaly I have found. See this idea is a combo of EAV & rollups (oracle). There is an anomaly.... Its hard to describe but as you roll up the traffic there are more "power sets" (permutations of "attributes"
http://en.wikipedia.org/wiki/Power_set meaning rolling up from day to month increases the number of rows). But it appears to be an anomaly that occurs in proportion to the complexity of attributes used (volume of traffic does not affect performance... thats the goal of the framework at the end of the day)... also attributes in my framwork by design are to be used scarcely (eg. to segment traffic so each user can get a report of just their traffic)