You can log all the commands that sets up the throttling by setting LOG_THROTTLE=true. Use directly in NodeJS # const throttle = Returns a promise Stop adding delay on localhost # throttle -stop -localhost This is useful if you run WebPageReplay and want to add some latency to your tests. Stopping is as easy as giving the parameter stop to throttle. You can start throttle with one of the premade profiles: throttle -profile 3gslow To make it easier we have pre made profiles, check them out by throttle –help: -profile Premade profiles, set to one of the following Remember: Throttle will use sudo so your user will need sudo rights. Here is an example for running with 3G connectivity. Start simulate a slower network connection # On OSX, add these lines to /etc/pf.conf if they don’t exist, to prevent the pfctl: Syntax error in config file: pf rules not loaded error when you try to run throttle pf_enable='YES' Upload/download is in kbit/s and RTT in ms. You can set the download/upload speed and/or RTT. You integrate it in your (web performance) tool to simulate different connections.You run it as a standalone tool setting simulate different connection speeds.It is usually used for two different things: Throttle uses pfctl on Mac and tc on Linux (you also need ip and route for Throttle to work on Linux) to simulate different network speeds and is inspired by tylertreat/Comcast, the connectivity setting in the WPTAgent and sltc.

Throttle lets you simulate slow network connections on Linux and Mac OS X. Run in Docker (on Linux) Introduction #.Start simulate a slower network connection.

Throttle emulator chrome mac