最近项目上需要在zuul网关进行限流,查阅了一些限流方案,比较好的方案是使用redis进行分布式限流,主要考虑到redis性能好,且redis本身是单线程操作,解决了并发问题。目前在github上开源的Spring Cloud Zuul RateLimit 就刚好满足了这些需求:https://github.com/marcosbarbero/spring-cloud-zuul-ratelimit,进而在项目中进入了这个组件,但是在性能压测的时候却发现性能表现不是很好,既然有问题,那就只能想办法解决问题或优化。
把源码拉下来研究源码是最直接的方式,说重点,我们在使用redis进行限流时,主要用到的是RedisRateLimiter这个类,而RedisRateLimiter继承了抽象类AbstractCacheRateLimiter,上代码:
public abstract class AbstractCacheRateLimiter implements RateLimiter {
@Override
public synchronized Rate consume(Policy policy, String key, Long requestTime) {
final Long refreshInterval = policy.getRefreshInterval();
final Long quota = policy.getQuota() != null ? SECONDS.toMillis(policy.getQuota()) : null;
final Rate rate = new Rate(key, policy.getLimit(), quota, null, null);
calcRemainingLimit(policy.getLimit(), refreshInterval, requestTime, key, rate);
calcRemainingQuota(quota, refreshInterval, requestTime, key, rate);
return rate;
}
protected abstract void calcRemainingLimit(Long limit, Long refreshInterval, Long requestTime, String key, Rate rate);
protected abstract void calcRemainingQuota(Long quota, Long refreshInterval, Long requestTime, String key, Rate rate);
}
RedisRateLimiter
public class RedisRateLimiter extends AbstractCacheRateLimiter {
private final RateLimiterErrorHandler rateLimiterErrorHandler;
private final RedisTemplate redisTemplate;
@Override
protected void calcRemainingLimit(Long limit, Long refreshInterval,
Long requestTime, String key, Rate rate) {
long begTime = System.currentTimeMillis();
if (limit != null) {
handleExpiration(key, refreshInterval, rate);
long