wrote:

The benefit in having the year window allows only having to go to a

single database as opposed to a potential 12 databases with month windows

Correct, if your resource instance has incurred usage in the last month,
but if no usage has been submitted for a resource instance since Jan for
example, then we still need to run a descending query back to Jan, giving
us a max of 12 database partitions to scan for old/inactive resource
instances when we do that in Dec (which is typically when people start to
get more interested in their yearly usage.)

but I think that probably doesn't outweigh having to duplicate the

yearly data on every document.

+1, that's what I was thinking.

- Jean-Sebastien

On Mon, Oct 12, 2015 at 5:57 PM, Benjamin Cheng <bscheng(a)us.ibm.com>
wrote:

I'm leaning towards agreeing with you in terms of reducing the number of
windows. I agree with what you've said on forever. The only case I can
point out is in years. The benefit in having the year window allows only
having to go to a single database as opposed to a potential 12 databases
with month windows, but I think that probably doesn't outweigh having to
duplicate the yearly data on every document.