-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Throttling #9
Comments
Won't that only emulate high latency? |
@MichielDeMey thanks for input! You are right - setTimeout will only emulate latency. I'm not sure how to correctly emulate bandwidth at this point, but I'd guess that it should be throttled somewhere around here (traffic-interceptor.js):
We can split each received data chunk into multiple smaller ones. |
http://thesmithfam.org/blog/2012/04/11/throttling-your-network-connection-on-mac-os-x/ maybe we can actually do it :) |
Note: to show the network throttling panel back again revert c002175 . |
You can use something like https://github.com/tjgq/node-stream-throttle (which uses https://github.com/jhurliman/node-rate-limiter) to throttle a stream. |
IMO doing a simple
setTimeout
on the proxy server should work just fine for most cases.The text was updated successfully, but these errors were encountered: