[11:41:31] <wikibugs>	 (03PS1) 10Hashar: Define npm peer dependency explicitly [extensions/TimedMediaHandler] - 10https://gerrit.wikimedia.org/r/368716 (https://phabricator.wikimedia.org/T172094)
[11:43:04] <wikibugs>	 (03PS1) 10Hashar: Define npm peer dependency explicitly [extensions/UploadWizard] - 10https://gerrit.wikimedia.org/r/368721 (https://phabricator.wikimedia.org/T172094)
[22:05:01] <brion>	 soon.... soon i will see how many CPUs i can actually parallelize ffmpeg over for vp9 :D
[23:11:37] <brion>	 hmm, so far i'm only seeing about 6 CPUs in use despite asking for 32 threads :(
[23:15:02] <brion>	 damn, looks like it only makes use of up to 8 threads for the columns at 3840x2160
[23:18:46] <brion>	 yeah, splitting files for encoding is gonna be the way to go
[23:26:22] <James_F>	 brion: Won't that mean that the encoding tree is not shared between the parts, making the total file size less efficient?
[23:26:56] <James_F>	 brion: (It's been a long while since I was properly into codec coding. ;-))
[23:27:21] <brion>	 James_F: there'd be a slight increase in file size at the boundary points yeah
[23:27:33] <brion>	 but relatively small
[23:27:39] * James_F nods.
[23:27:39] <brion>	 everything resets at keyframes
[23:28:05] <brion>	 hmmmm, bleeding-edge libvpx should parallelize better to 16 threads, maybe even 32
[23:28:16] <brion>	 now to figure out how to compile ffmpeg with that