Puppeteer is a side-scrolling platformer in which the player controls the character ‘Kutaro. Its presentation is unorthodox, and as such, it’s unlike anything I’ve played before. While the periphery of the stage and its red curtain can at first be quite frustrating to look at – it does cut off parts of the screen, after all - I quickly come to realize that it’s all part of Puppeteer’s charm. The action is viewed through the lens of an unseen audience, with their laughter, gasps, and occasional applause complementing everything you do. log( "CHILD: url received from parent process", url) Ĭonst browser = await puppeteer.Puppeteer’s faux stagecraft style is a big part of what makes it so accessible and, in turn, so endearing. The code snippet below is a simple example of running parallel downloads with Puppeteer.Ĭonst downloadPath = path. □ If you are not familiar with how child process work in Node I highly encourage you to give this article a read. We can combine the child process module with our Puppeteer script and download files in parallel. Child process is how Node.js handles parallel programming. We can fork multiple child_proces in Node. Our CPU cores can run multiple processes at the same time. □ Learn more about the single threaded architecture of node here Therefore if we have to download 10 files each 1 gigabyte in size and each requiring about 3 mins to download then with a single process we will have to wait for 10 x 3 = 30 minutes for the task to finish. It can only execute one process at a time. You see Node.js in its core is a single-threaded system. However, if you have to download multiple large files things start to get complicated. In this next part, we will dive deep into some of the advanced concepts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |