There is a trend of browser launch taking longer with each new release of Puppeteer/Chrome.Here is a tabular breakdown of those results (Red = Slow, Green = Fast). In terms of the versions that we decided to test, we went all the way back to version 1.20.0 of Puppeteer and tested up until 19.3.0 (the latest release at the time). Remember: we just want to get a sense of what version of Chrome/Puppeteer to use for a particular task. We do acknowledge that this isn’t perfect but such things never are when you can’t control every piece of networking in the world. Because of that, our tool allows you to run a test numerous times to try and remove some of that noise variance from the final results. It should be acknowledged that the results of these tests will vary depending on the webpage, network speed, latency, frontend technology and hardware resources. How long it takes Puppeteer to be able to select an h1 element after the page was created Uses Chrome’s internal window.performance object to get the time at which the browser started rendering DOM objects - like actual text or images Uses Chrome’s internal window.performance object to get the time at which the browser started rendering something - like a background color Uses Chrome’s internal window.performance object to get the time at which the Document triggered its DOMContentLoaded event. Uses Chrome’s internal window.performance object to get the time of the browser’s first received byte - be it from a server response, cache, or local resource How long it takes to render a PDF of the page and save it. How long it takes Puppeteer to close and kill the Chrome process How long it takes to screenshot and save the page. Navigation is considered finished when the page’s Body element triggers the load event Each version is using its recommended Chromium revision. How long Puppeteer takes to launch a Chrome browser. Here is a quick overview of the tasks that we decided to tests and some details about them: To that end, we’ve open sourced a tool that you can use to test the different common tasks to see which version is ideal for your application. We’ve actually heard about this from our users a lot, and wanted to spend some time figuring which version works best for certain tasks. If you aren’t familiar with what you can with Puppeteer, check out our article here.įor those of you that are already using Puppeteer in your day-to-day, you might have noticed that as new versions of Puppeteer are released you notice performance gains and degradations depending on the version of Chromium it comes bundled with. We work with Puppeteer a lot at Browserless to ensure we can help companies get the most out of browser automation tasks at scale. As it stands today there are over 82,000 stars and 8,800 forks of the project plus hundreds of contributors. One of the most important open source projects for headless automation is Puppeteer. ![]() ![]() ![]() Subscribe to our blog if you’d like to get the results of future puppeteer versions in the future.We open sourced the tool that we built in case you want to test for yourself!.faster, and are continuing to update these as releases are made. We published some results which can help you scrape, automate, test, etc. ![]()
0 Comments
Leave a Reply. |