From f1ec469fd467687780c5303a97acfb0acb08f8d0 Mon Sep 17 00:00:00 2001 From: Pinapelz Date: Mon, 24 Jul 2023 20:43:49 -0700 Subject: Add speed stats to patchwork-2 --- src/content/blog/patchwork-posts/patchwork-archive-2.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'src') diff --git a/src/content/blog/patchwork-posts/patchwork-archive-2.md b/src/content/blog/patchwork-posts/patchwork-archive-2.md index 7b1e314..82a992d 100644 --- a/src/content/blog/patchwork-posts/patchwork-archive-2.md +++ b/src/content/blog/patchwork-posts/patchwork-archive-2.md @@ -322,8 +322,11 @@ Yep. 100% CPU usage. Turns out FFMPEG can be pretty CPU intensive, the process o I ended up just making do with the speed. Bilibili isn't exactly a priority for me either, so I'm fine with it taking a while to download and convert videos. (The entire worker flow is queue based too, I'll touch on this another time) +### Speed +I run 2 workers, both of which pull from the same queue of videos to download. With the current setup, I'm able to average around `3 videos per minute` (180 videos per hour) for YouTube videos. Obviously if Bilibili videos are in the queue, the speed will be much slower. + ## That's all for now -That's pretty much all I got to say about how I initially sourced content and how the workers archive it. In the next part I'll get more into the details regarding storage and serving the content. +That's all I got to say about how I initially sourced content and how the workers archive it. In the next part I'll get more into the details regarding storage and serving the content. -- cgit v1.2.3