This performance consumption generally has no impact. However, it is quite unpleasant that setInterval has errors. It is recommended to use setTimeout recursion as much as possible.
setInterval alone does not consume much. The key is whether there are any expensive operations after the scheduled trigger. To be on the safe side, you should clear it after use.
This depends on what you use setInterval for! If you just do some simple operations and nothing happens, and if you keep requesting the interface, the performance will definitely not be very good. Just like what I said on the first floor, remember to clear it if you don’t need it! WebView (network view) can load and display web pages and can be regarded as a browser. It uses the WebKit rendering engine to load and display web pages.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Remember clearInterval when not in use
This performance consumption generally has no impact. However, it is quite unpleasant that setInterval has errors. It is recommended to use setTimeout recursion as much as possible.
setInterval alone does not consume much. The key is whether there are any expensive operations after the scheduled trigger. To be on the safe side, you should clear it after use.
This depends on what you use setInterval for! If you just do some simple operations and nothing happens, and if you keep requesting the interface, the performance will definitely not be very good. Just like what I said on the first floor, remember to clear it if you don’t need it!
WebView (network view) can load and display web pages and can be regarded as a browser. It uses the WebKit rendering engine to load and display web pages.