Debouncing is a programming practice used to ensure that time-consuming tasks do not fire so often, that it stalls the performance of the web page. In other words, it limits the rate at which a function gets invoked.
Example: Here is a simple implementation of debouncing.
Output: Alertbox after 3 seconds
Hello No matter how many times you click the debounce button, I get executed once every 3 seconds!!
Explanation: The button is attached to an event listener that calls the debounce function. The debounce function is provided with 2 parameters – a function and a Number. Declared a variable debounceTimer, which as the name suggests, is used to actually call the function, received as a parameter after an interval of ‘delay’ milliseconds.
If the debounce button is clicked only once, the debounce function gets called after the delay. However, if the debounce button is clicked once, and again clicked prior to the end of the delay, the initial delay is cleared and a fresh delay timer is started. The clearTimeout function is being used to achieve it.
The general idea for debouncing is:
- Start with 0 timeout
- If the debounced function is called again, reset the timer to the specified delay
- In case of timeout, call the debounced function Thus every call to a debounce function, resets the timer and delays the call.
Application: Debouncing can be applied in implementing suggestive text, where we wait for the user to stop typing for a few seconds before suggesting the text. thus, on every keystroke, we wait for some seconds before giving out suggestions. Another application of debouncing is in content-loading webpages like Facebook and Twitter where the user keeps on scrolling. In these scenarios, if the scroll event is fired too frequently, there might be a performance impact, as it contains lots of videos and images. Thus the scroll event must make use of debouncing.