Add “maxuploadtargettimeframe” to change the timeframe considered by “maxuploadtarget” #30176

issue lcharles123 openend this issue on May 25, 2024
  1. lcharles123 commented at 11:39 pm on May 25, 2024: none

    Please describe the feature you’d like to see added.

    The “maxuploadtarget” #Tries to keep outbound traffic under the given target per 24h (one day).

    But many ISPs that does not have unlimited traffic, account it by month. So it will be a handy setting to avoid the calculating of the amount transferred in the billing period. This new setting can be specified in days.

  2. lcharles123 added the label Feature on May 25, 2024
  3. willcl-ark commented at 8:18 am on June 27, 2024: member

    Would it not be easier here to simply divide the monthly allowance by the number of days in the month, and use this as the maxuploadtarget?

    Adding a redundant second setting vs just calculating a daily target doesn’t make much sense to me. Even if we did add a monthly target (specified in days), then many months have different numbers of days in them, so this new handy setting will be wrong for many of them.

    The best solution for you would seem to be to divide your monthly allowance by the number of days in the longest month (31) and set this as the maxuploadtarget. This way you will be on target in long months, and slighty under target in shorter months.

    Please let me know if I’m misunderstanding something, otherwise I think we can close this out.

  4. maflcko commented at 7:33 am on July 1, 2024: member
    Closing for now, per previous comment.
  5. maflcko closed this on Jul 1, 2024


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2024-12-21 15:12 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me