2014-12-12 - Re: [GRASE-Hotspot] Add Data to Limit

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 4d9672146e25e91f330a74451962e4eb6543f3a821ce845cf6c908cd09a6acc5
Message ID: <CAESLx0+Ygpo1EBA5oztH+mKEkcsXtUgM2zepnV0+22uwrxJLWw@mail.gmail.com>
Reply To: <d3a85d94-6456-4a5b-ae8b-139de875591c@grasehotspot.org>
UTC Datetime: 2014-12-12 19:13:19 UTC
Raw Date: Sat, 13 Dec 2014 12:13:19 +1000

Raw message 

Not quite.

It's a little hard to explain. The recurring data limits are dynamic, in
that they are calculated on a dynamic range of usage. At the rollover of
the month, it just starts calculating based on the usage from the 1st of
the month.
The normal Data limit is calculated on the lifetime of the account, except
to make it easier we compact the "lifetime" every month. We compact
everything older than about 2 months, as this works best in most situations
for still seeing last months logs. What this means, is if you have a 20Gb
data limit, it calculates based on this months usage and last months. At
the end of the month, we compact everything older than 2 months, put the
monthly totals into another table, and subtract the new monthly totals from
the current data limit. E.g. if you used 2Gb 3 months ago, and we run the
compaction, your datalimit will now display as 18Gb in the admin interface.
However, when you login, it'll display as 18Gb minus what you have used
this month and last month.

When working out what you data limit should be, at login it calculates the
recurring data limit, and the normal data limit, and if either limit is
reached, it prevents you logging in.

So in your example, if your user has used 40Gb this month (with no previous
months), with a 40Gb recurring limit, and you "add" 20Gb, they will still
not be able to login as they have exceeded the 20Gb "lifetime" limit. Next
month they will also not be able to login, and the month after when
compaction runs, their data limit will become -20Gb (which is just set to 0
I believe). Effectively, you'll lock them out permanently.

Some better documentation is probably needed.

Sometimes it makes sense combining recurring limits and normal limits
together. E.g. a 30Gb quota but limited to 2 hours a day; think teenage
child, they can waste their quota if they wish, or can stretch it out over
however long they like.

Tim

On Fri, Dec 12, 2014 at 12:16 PM, Derek Mitchell <de***2@gmail.com>
wrote:
>
> Thanks Tim, So if they are on the 40Gb recurring limit and you add 20Gb
> using the "Add Data to Limit" option, when it resets at the end of the
> month they will only have 20Gb instead of 40.
>
> Thanks
> Derek
>
> On Friday, December 12, 2014 12:05:24 PM UTC+10, timwhite88 wrote:
>>
>> Hi Derek
>>
>> The way the limits work, is if any limit is reached, they are cut off. If
>> you add a data limit to someone with a recurring limit, they'll suddenly be
>> limited to that data limit. So in your situation, say they'd used 30Gb for
>> the month, and you applied a limit of 20Gb, they would have already reached
>> that limit and so will be cut off. If you applied a limit of 60Gb to the
>> account, and they have a recurring limit of 40 per month, they'll be
>> limited to 40Gb this month, and assuming they use it all, then next month
>> they'll be limited to 20Gb.
>>
>> It's much more difficult to give someone "bonus" data until the end of
>> the month.
>> What I normally do in these situations, is create a second user for their
>> bonus data that expires at the end of the month.
>>
>> Tim
>>
>> On Fri, Dec 12, 2014 at 11:59 AM, Derek Mitchell <de***.@gmail.com>
>> wrote:
>>
>>> Hi, If you "Add Data to Limit" under a user that is on a 40Gb monthly
>>> recurring data limit, will that just add data for the user until the end of
>>> the month when the limits are reset or will it add to the recurring 40Gb
>>> already specified in the group setting? If you add 20Gb to the data limit
>>> will it then allow the user to have 60Gb per month from then on or will it
>>> reset back to 40Gb at the end of the month?
>>>
>>> Regards,
>>> Derek
>>>
>>> --
>>> This mailing list is for the Grase Hotspot Project
>>> http://grasehotspot.org
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Grase Hotspot" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to gr***.@grasehotspot.org.
>>> To post to this group, send email to gr***.@grasehotspot.org.
>>> Visit this group at http://groups.google.com/a/
>>> grasehotspot.org/group/grase-hotspot/.
>>> To view this discussion on the web visit https://groups.google.com/a/
>>> grasehotspot.org/d/msgid/grase-hotspot/3ca98551-2f4b-
>>> 4783-b035-508fb3a70f23%40grasehotspot.org
>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/3ca98551-2f4b-4783-b035-508fb3a70f23%40grasehotspot.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>  --
> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
> ---
> You received this message because you are subscribed to the Google Groups
> "Grase Hotspot" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gr***e@grasehotspot.org.
> To post to this group, send email to gr***t@grasehotspot.org.
> Visit this group at
> http://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
> To view this discussion on the web visit
> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/d3a85d94-6456-4a5b-ae8b-139de875591c%40grasehotspot.org
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/d3a85d94-6456-4a5b-ae8b-139de875591c%40grasehotspot.org?utm_medium=email&utm_source=footer>
> .
>

Thread