diff options
| author | Pinapelz <donaldshan1@outlook.com> | 2023-07-24 20:43:49 -0700 |
|---|---|---|
| committer | Pinapelz <donaldshan1@outlook.com> | 2023-07-24 20:43:49 -0700 |
| commit | f1ec469fd467687780c5303a97acfb0acb08f8d0 (patch) | |
| tree | bc3fb2a0800fcf0037d82149eb3e7a3b9b8a1ef4 | |
| parent | 22be648e72eac8f1e1ea4a977f086eadddf2ed3a (diff) | |
Add speed stats to patchwork-2
| -rw-r--r-- | src/content/blog/patchwork-posts/patchwork-archive-2.md | 5 |
1 files changed, 4 insertions, 1 deletions
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. |