{"_id":"55356d8ee3f0920d004f5c54","__v":7,"version":{"_id":"550ada9d921b7d0d00228876","forked_from":"550a3b2542fff40d00ae5ffb","project":"550a379f635c660d00527fd8","__v":3,"createdAt":"2015-03-19T14:18:05.245Z","releaseDate":"2015-03-19T14:18:05.245Z","categories":["550ada9d921b7d0d00228877","550ada9d921b7d0d00228878","550ada9d921b7d0d00228879","550ada9d921b7d0d0022887a","550ada9d921b7d0d0022887b","550ada9d921b7d0d0022887c","550ada9d921b7d0d0022887d","5523e61e71c0542100993493","55246f72ccc28a0d0062c560"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"3.0.0","version":"3.0.0"},"project":"550a379f635c660d00527fd8","user":"550a378e635c660d00527fd7","category":{"_id":"55246f72ccc28a0d0062c560","version":"550ada9d921b7d0d00228876","__v":1,"pages":["55356d8ee3f0920d004f5c54"],"project":"550a379f635c660d00527fd8","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-04-07T23:59:46.143Z","from_sync":false,"order":3,"slug":"general-usage","title":"General Usage"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-04-20T21:20:14.836Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":999,"body":"## The default settings\n\nBy default Snoocore will throttle all calls by one request every 1 second (1000 milliseconds). This can be adjusted by setting the `throttle` variable in the [Configuration Options](doc:configuration-options).\n\nThis default is great for newcomers as it will \"just work\" in a consistent way; however, more advance usage can be had by setting this value lower or disabling it all together allowing for \"burst requests\"\n\n## Burst requests\n\nSet the `throttle` variable to a value less than 1000 milliseconds (or even 0) and if the rate limit is reached, Snoocore will wait the appropriate amount of time before making another request. It does this by looking at the rate limit headers sent back from reddit (See [Events](doc:events) for rate limit events that can be listened to).\n\n## Multiple Instances\n\nIf you are running Snoocore across multiple instances, the rate limit will still be respected via the rate limit headers.\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Note\",\n  \"body\": \"Currently there isn't an option to circumvent the rate limit headers to mitigate abuse. If there is an appropriate use case an open an issue on GitHub or chat about it on Gitter.\"\n}\n[/block]","excerpt":"","slug":"throttle","type":"basic","title":"Throttle Options"}
## The default settings By default Snoocore will throttle all calls by one request every 1 second (1000 milliseconds). This can be adjusted by setting the `throttle` variable in the [Configuration Options](doc:configuration-options). This default is great for newcomers as it will "just work" in a consistent way; however, more advance usage can be had by setting this value lower or disabling it all together allowing for "burst requests" ## Burst requests Set the `throttle` variable to a value less than 1000 milliseconds (or even 0) and if the rate limit is reached, Snoocore will wait the appropriate amount of time before making another request. It does this by looking at the rate limit headers sent back from reddit (See [Events](doc:events) for rate limit events that can be listened to). ## Multiple Instances If you are running Snoocore across multiple instances, the rate limit will still be respected via the rate limit headers. [block:callout] { "type": "warning", "title": "Note", "body": "Currently there isn't an option to circumvent the rate limit headers to mitigate abuse. If there is an appropriate use case an open an issue on GitHub or chat about it on Gitter." } [/block]