![]() You can find a helpful list of these Chrome switches with their explanations here. ![]() This will help Puppeteer to consume less memory and start faster. This removes all the extras that are probably unnecessary for your screenshot script - although you may need to tweak these settings based on your specific needs. You can run Puppeteer with minimal settings. Some of this can be achieved via Puppeteer settings, but some will come from optimizing the actual pages you are rendering. Most likely, the biggest speed gains will come from getting your target pages to render faster. When optimizing Puppeteer, remember that there are only so many ways to speed up the startup/shutdown performance of Puppeteer itself. This advice is less applicable if you are doing general screenshots of public websites, but some of the tips will still be helpful! This advice is mostly applicable if you are performing some kind of internal screenshot process in your app, using web pages under your control. If you're working with Puppeteer and trying to squeeze more performance out of it, here are some things you can try.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |