Skip to content
#

rate-limiting

Here are 380 public repositories matching this topic...

LeoMe1
LeoMe1 commented Feb 11, 2022

Issue Description

ConcurrentLinkedHashMap在构造二维数组时会根据CPU核心数来计算出当前数组的一维下标长度,当核数为96时,下标为128,此时单个ParameterMetric对象大小接近1M,如下图所示:

image

当接口调用量较大时,此处将会占用大量内存,sentinel是否有考虑过这块的内存使用,或者切成其他Cache?毕竟googlecode.concurrentlinkedhashmap作者也建议使用Caffeine了.

Tell us your environment

springbo

nginxconfig.io
RebelliousWhiz
RebelliousWhiz commented Dec 29, 2021

Sorry for not following the template. It's a straightforward question.

By enabling "WordPress-specific rules", the following codes will be added to the wordpress.conf:

# WordPress: deny general stuff
location ~* ^/(?:xmlrpc\.php|wp-links-opml\.php|wp-config\.php|wp-config-sample\.php|readme\.html|license\.txt)$ {
    deny all;
}

However, this disables xmlrpc feature, which disa

sentinel-golang
Beebeeoii
Beebeeoii commented Jul 18, 2021

🚀 Feature Proposal

Have an option to slow down responses instead of returning 429 errors.

Motivation

By having the option to slow down responses would deter scrapping of data from a server which would put an additional load on the server while still enabling responses for cases where user may not be actually scrapping, but just that there are many machines surfing the webpage under

A Guzzle middleware that can throttle requests according to (multiple) defined rules. It is also possible to define a caching strategy, e.g. get the response from cache when the rate limit is exceeded or always get a cached value to spare your rate limits. Using wildcards in host names is also supported.

  • Updated Sep 21, 2021
  • PHP

Improve this page

Add a description, image, and links to the rate-limiting topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the rate-limiting topic, visit your repo's landing page and select "manage topics."

Learn more