nadylib/leaky-bucket
最新稳定版本:0.1.0
Composer 安装命令:
composer require nadylib/leaky-bucket
包简介
An fiber-based implementation of the LeakyBucket algorithm
README 文档
README
An async Leaky Bucket implementation using the Revolt EventLoop
Usage
use Nadylib\LeakyBucket\LeakyBucket; $bucket = new Nadylib\LeakyBucket\LeakyBucket( size: 5, refillDelay: 1.0, refillAmount: 1 );
There is only 1 function of interest: LeakyBucket::take(<amount>):
use Nadylib\LeakyBucket\LeakyBucket; $bucket = new Nadylib\LeakyBucket\LeakyBucket( size: 5, refillDelay: 1.0, refillAmount: 1 ); for ($i = 1; $i <= 7; $i++) { $bucket->take(1); $time = (new DateTimeImmutable())->format("H:i:s.v"); echo("[{$time}] Taken.\n"); }
The first 5 takes will take immediately, while 6 and 7 take 1s each. There is no sleep involved, just async fibers, so this is absolutely safe to use.
use Nadylib\LeakyBucket\LeakyBucket; use Revolt\EventLoop; $bucket = new Nadylib\LeakyBucket\LeakyBucket( size: 5, refillDelay: 1.0, refillAmount: 1 ); for ($i = 1; $i <= 7; $i++) { $bucket->take(callback: function() { $time = (new DateTimeImmutable())->format("H:i:s.v"); echo("[{$time}] Taken.\n"); }); } EventLoop::run();
This will behave exactly the same, but the call to $bucket->take() will always return immediately.
When using the callback version, make sure to call EventLoop::run() at the end, because the main fiber/thread is never suspended, but always returns immediately, so you have to make sure the event loop finishes its work. In a real world environment, this will not be necessary, because your code will run in a global event loop anyway.
统计信息
- 总下载量: 29.23k
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 1
- 依赖项目数: 1
- 推荐数: 0
其他信息
- 授权协议: AGPL-3.0-or-later
- 更新时间: 2024-04-28