Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: <arek@chelmnet.pl>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Dynamic Ratelimiting
Date: Sat, 27 Dec 2003 01:43:03 +0000	[thread overview]
Message-ID: <marc-lartc-107249142302703@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107219671428584@msgid-missing>

> I am working in a script to do something like that, can you post 
> your script
> for us?

I have my own hard-stuff for solve that problem.

I measure all of my clients for long time (tc+parser+sql)
After some period of time, 90% of my LAN clients get large autmated bandwidth speeds , thus the rest about 10% has much worst speeds.
My system increase/decrese client speeds based on per client policy (kept in DB):

It is Per User Policy :
 Array (  "LBS_TBS_MAX_ANDOR" => Array (  "T1"=>"OR",  "NIGHT"=>"OR",  "COMB"=>"OR",  ),  "LBS_TBS_MIN_ANDOR" => Array (  "T1"=>"AND",  "NIGHT"=>"AND",  "COMB"=>"AND",  ),  "LBS_MIN_OK" => Array (  "T1"=>"2000",  "NIGHT"=>"1500",  "COMB"=>"4000",  ),  "LBS_MAX_OK" => Array (  "T1"=>"4000",  "NIGHT"=>"5000",  "COMB"=>"9000",  ),    "TBS_MIN_OK" => Array (  "T1"=>"1800",  "NIGHT"=>"2000",  "COMB"=>"4000",  ),  "TBS_MAX_OK" => Array (  "T1"=>"3000",  "NIGHT"=>"2500",  "COMB"=>"8000",  ),  "INC_STEP" => Array (  "T1"=>"10",  "NIGHT"=>"0",  "COMB"=>"0",  ),   "DEC_STEP" => Array (  "T1"=>"30",  "NIGHT"=>"30",  "COMB"=>"3",  ),    "MAX_SPD" => Array (  "T1"=>"150",  "NIGHT"=>"150",  "COMB"=>"150",  ),  "MIN_SPD" => Array (  "T1"=>"50",  "NIGHT"=>"50",  "COMB"=>"50",  ),  "LBS_DELTA_MIN" => Array (  "T1"=>"3600",  "NIGHT"=>"3600",  "COMB"=>"3600",  ),   ) 

The speeds are collected that way in MYSQL:
 Array ( "TB" => Array (  "COMB"=>"22739678964", "T1"=>"3339908691", "COMBNIGHT"=>"33319656215", "NIGHT"=>"5217145438", "COMBLNIGHT"=>"6016054440", "LNIGHT"=>"1541492392", "COMBT1"=>"0", ), "LB" => Array (  "COMB"=>"416211349", "T1"=>"201458741", "COMBNIGHT"=>"395545975", "NIGHT"=>"228162616", "COMBLNIGHT"=>"2270334036", "LNIGHT"=>"3614076", "COMBT1"=>"88073956", ), "TT" => Array (  "COMB"=>"7290365", "T1"=>"10701292", "COMBNIGHT"=>"6348749", "NIGHT"=>"8714890", "COMBLNIGHT"=>"4005954", "LNIGHT"=>"7909108", "COMBT1"=>"0", ), "LD" => Array (  "COMB"=>"33763", "T1"=>"33763", "COMBNIGHT"=>"25194", "NIGHT"=>"25194", "COMBLNIGHT"=>"27538", "LNIGHT"=>"27538", "COMBT1"=>"8880", ), "TS" => Array (  "COMB"=>"1072420867", "T1"=>"1072420867", "COMBNIGHT"=>"1072454577", "NIGHT"=>"1072454577", "COMBLNIGHT"=>"1072393354", "LNIGHT"=>"1072393354", "COMBT1"=>"1056198868", ),  ) 


Which i can see from user-level managment appz:
hub3:~# abo "inder Ark" all


 192.168.190.122; Binder Arkadiusz * sqix * sqix@chelmnet.pl *
xxxxxx87,3xxxx82 * hub3.xxxxx.pl * 00:50:xxxx:51:65 * CI50/24 [CI50B-I] * SPD87 * FIXED
(as you can see currently i have EIR‡ Kbits), yesterday i had over 130 Kbits, just because i downloaded too-much as T1 policy (201.46Mb).
But tommorrow i will have it back !

PRECIOSION-INFORMATIONS:
* T_WHEN_CONNECTED= 2002-06-30
* T_WHO_CONNECTED= Szarmach
* A_RECORD_CREATE_DATE= 2002-06-14-10-56-32
* A_RECORD_CREATE_AUTHOR= bzyk
* N_AVG_TRAFFIC = {
Total_BYTES(COMB) 22.74_Gbytes, during 2.81_Months AVG_T=3.12_kbps
Last Bytes(COMB) 416.21_Mbytes, during 9.38_Hours L_AVG_T\x12.33_kbps
 Updated 2003-12-26 17:3.50
Total_BYTES(T1) 3.34_Gbytes, during 4.13_Months AVG_T12.10_bps
Last Bytes(T1) 201.46_Mbytes, during 9.38_Hours L_AVG_T=5.97_kbps
 Updated 2003-12-26 17:3.50
Total_BYTES(COMBNIGHT) 33.32_Gbytes, during 2.45_Months AVG_T=5.25_kbps
Last Bytes(COMBNIGHT) 395.55_Mbytes, during 7.00_Hours L_AVG_T\x15.70_kbps
 Updated 2003-12-27 0:2.51
Total_BYTES(NIGHT) 5.22_Gbytes, during 3.36_Months AVG_TY8.65_bps
Last Bytes(NIGHT) 228.16_Mbytes, during 7.00_Hours L_AVG_T=9.06_kbps
 Updated 2003-12-27 0:2.51
Total_BYTES(COMBLNIGHT) 6.02_Gbytes, during 1.55_Months AVG_T=1.50_kbps
Last Bytes(COMBLNIGHT) 2.27_Gbytes, during 7.65_Hours L_AVG_T‚.44_kbps
 Updated 2003-12-26 7:41.32
Total_BYTES(LNIGHT) 1.54_Gbytes, during 3.05_Months AVG_T\x194.90_bps
Last Bytes(LNIGHT) 3.61_Mbytes, during 7.65_Hours L_AVG_T\x131.24_bps
 Updated 2003-12-26 7:41.32
Total_BYTES(COMBT1) 0.00_bytes, during 1.00_secs AVG_T=0.00_bps
Last Bytes(COMBT1) 88.07_Mbytes, during 2.47_Hours L_AVG_T=9.92_kbps
 Updated 2003-6-21 17:2.28
                  } = TOTAL_AVERAGE 1.68_k_bps
hub3:~#


If anyone is interested in such stuff
visit http://nsm.pl/~arek/superedit -for other shots
and contact me.

I can't put it free, just because i've been writing that for 2 years, but i can share with other such projects/communities.

A.Binder

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-12-27  1:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 16:16 [LARTC] Dynamic Ratelimiting David DeLauro
2003-12-23 20:28 ` Damjan
2003-12-26 15:18 ` Anderson O Muniz
2003-12-27  1:43 ` arek [this message]
2003-12-29 14:42 ` Anderson O Muniz
2003-12-29 15:08 ` David DeLauro
2003-12-29 15:11 ` David DeLauro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-107249142302703@msgid-missing \
    --to=arek@chelmnet.pl \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox