Knowledge (XXG)

Rate limiting

Source 📝

174:
limiting at the hypervisor layer. Two important performance metrics of rate limiters in data centers are resource footprint (memory and CPU usage) which determines scalability, and precision. There usually exists a trade-off, that is, higher precision can be achieved by dedicating more resources to the rate limiters. A considerable body of research with focus on improving performance of rate limiting in data centers.
173:
Data centers widely use rate limiting to control the share of resources given to different tenants and applications according to their service level agreement. A variety of rate limiting techniques are applied in data centers using software and hardware. Virtualized data centers may also apply rate
157:
However, in some cases (i.e. web servers) the session management and rate limiting algorithm should be built into the application (used for dynamic content) running on the web server, rather than the web server itself.
335: 415: 161:
When a protocol server or a network device notice that the configured request limit is reached, then it will offload new requests and not respond to them. Sometimes they may be added to a
165:
to be processed once the input rate reaches an acceptable level, but at peak times the request rate can even exceed the capacities of such queues and requests have to be thrown away.
143:, for session management. A rate limiting algorithm is used to check if the user session (or IP address) has to be limited based on the information in the session cache. 331: 86:
While a hardware appliance can limit the rate for a given range of IP-addresses on layer 4, it risks blocking a network with many users which are masked by
385: 308: 365: 76: 467: 437: 35: 147: 87: 50: 151: 95: 105: 39: 225: 299: 215: 162: 101: 220: 20: 272: 188: 183: 140: 109: 57: 397: 132: 129: 104:
can be used to filter on the session layer but will effectively disarm encryption protocols like
361: 80: 19:
This article is about computer networks. For the rate-limiting step in chemical kinetics, see
407: 298: 27: 75:
Rate limiting can be induced by the network protocol stack of the sender due to a received
358:
Cloud Native Using Containers, Functions, and Data to Build Next-Generation Applications
193: 242: 461: 210: 205: 43: 237: 332:"Mitigating HTTP GET Flooding Attacks through Modified NetFPGA Reference Router" 247: 411: 125: 121: 91: 49:
Research indicates flooding rates for one zombie machine are in excess of 20
69: 68:
Hardware appliances can limit the rate of requests on layer 4 or 5 of the
330:
Jinghe Jin; Nazarov Nodir; Chaetae Im; Seung Yeob Nam (7 November 2014).
252: 386:"Datacenter Traffic Control: Understanding Techniques and Trade-offs" 402: 146:
In case a client made too many requests within a given time frame,
136: 112:
between the appliance and the protocol server (i.e. web server).
34:
is used to control the rate of requests sent or received by a
300:"An Absurdly Basic Bug Let Anyone Grab All of Parler's Data" 418:
from the original on Jan 16, 2024 – via ResearchGate.
120:
Protocol servers using a request / response model, such as
384:
Noormohammadpour, M.; Raghavendra, C. S. (May 2018).
53:
GET requests per second, legitimate rates much less.
273:"Cisco Router Firewall Security: DoS Protection" 379: 377: 60:to minimize the number of throttling errors. 16:Limiting the data rate on network controllers 8: 390:IEEE Communications Surveys & Tutorials 438:"An alternative approach to rate limiting" 401: 56:Rate limiting should be used along with 263: 431: 429: 427: 425: 271:Richard A. Deal (September 22, 2004). 243:ASP.NET Core rate limiting middleware 150:servers can respond with status code 7: 311:from the original on 12 January 2021 248:Rate limiting for .NET (PCL Library) 297:Greenberg, Andy (12 January 2021). 14: 338:from the original on Mar 6, 2023 436:Nikrad Mahdi (April 12, 2017). 79:-marked packet and also by the 83:of any router along the way. 1: 238:ASP.NET Web API rate limiter 38:. It can be used to prevent 36:network interface controller 484: 412:10.1109/COMST.2017.2782753 18: 346:– via ResearchGate. 253:Rate limiting for Node.JS 360:. O'Reilly Media. 2019. 226:Sliding window counter 152:429: Too Many Requests 102:Deep packet inspection 21:Rate-determining step 216:Fixed window counter 189:Bandwidth throttling 184:Bandwidth management 468:Network performance 64:Hardware appliances 221:Sliding window log 133:key-value database 128:may use a central 58:throttling pattern 81:network scheduler 28:computer networks 475: 453: 452: 450: 448: 433: 420: 419: 405: 381: 372: 371: 354: 348: 347: 345: 343: 327: 321: 320: 318: 316: 302: 294: 288: 287: 285: 283: 268: 116:Protocol servers 483: 482: 478: 477: 476: 474: 473: 472: 458: 457: 456: 446: 444: 435: 434: 423: 383: 382: 375: 368: 356: 355: 351: 341: 339: 329: 328: 324: 314: 312: 296: 295: 291: 281: 279: 270: 269: 265: 261: 180: 171: 118: 66: 24: 17: 12: 11: 5: 481: 479: 471: 470: 460: 459: 455: 454: 421: 373: 366: 349: 322: 289: 262: 260: 257: 256: 255: 250: 245: 240: 234: 233: 229: 228: 223: 218: 213: 208: 202: 201: 197: 196: 194:Project Shield 191: 186: 179: 176: 170: 167: 117: 114: 90:with a single 65: 62: 15: 13: 10: 9: 6: 4: 3: 2: 480: 469: 466: 465: 463: 443: 439: 432: 430: 428: 426: 422: 417: 413: 409: 404: 399: 395: 391: 387: 380: 378: 374: 369: 367:9781492053798 363: 359: 353: 350: 337: 334:. p. 1. 333: 326: 323: 310: 306: 301: 293: 290: 278: 274: 267: 264: 258: 254: 251: 249: 246: 244: 241: 239: 236: 235: 231: 230: 227: 224: 222: 219: 217: 214: 212: 209: 207: 204: 203: 199: 198: 195: 192: 190: 187: 185: 182: 181: 177: 175: 168: 166: 164: 159: 155: 153: 149: 144: 142: 138: 134: 131: 127: 124:or typically 123: 115: 113: 111: 107: 103: 99: 97: 93: 89: 84: 82: 78: 73: 71: 63: 61: 59: 54: 52: 47: 45: 41: 37: 33: 32:rate limiting 29: 22: 445:. Retrieved 441: 393: 389: 357: 352: 340:. Retrieved 325: 313:. Retrieved 304: 292: 280:. Retrieved 276: 266: 211:Leaky bucket 206:Token bucket 172: 169:Data centers 160: 156: 145: 119: 100: 85: 74: 67: 55: 48: 44:web scraping 31: 25: 342:19 December 277:Cisco Press 126:Web servers 122:FTP servers 40:DoS attacks 403:1712.03530 315:12 January 259:References 200:Algorithms 92:IP address 42:and limit 447:April 16, 282:April 16, 232:Libraries 141:Aerospike 130:in-memory 70:OSI model 462:Category 416:Archived 396:(2): 1. 336:Archived 309:Archived 178:See also 135:, like 442:Medium 364:  94:of an 398:arXiv 305:Wired 163:queue 137:Redis 449:2017 362:ISBN 344:2021 317:2021 284:2017 148:HTTP 108:and 51:HTTP 408:doi 139:or 110:SSL 106:TLS 98:. 96:ISP 88:NAT 77:ECN 72:. 26:In 464:: 440:. 424:^ 414:. 406:. 394:20 392:. 388:. 376:^ 307:. 303:. 275:. 154:. 46:. 30:, 451:. 410:: 400:: 370:. 319:. 286:. 23:.

Index

Rate-determining step
computer networks
network interface controller
DoS attacks
web scraping
HTTP
throttling pattern
OSI model
ECN
network scheduler
NAT
IP address
ISP
Deep packet inspection
TLS
SSL
FTP servers
Web servers
in-memory
key-value database
Redis
Aerospike
HTTP
429: Too Many Requests
queue
Bandwidth management
Bandwidth throttling
Project Shield
Token bucket
Leaky bucket

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.