If you are going to use 2160p/H265 of course the processing is going to be slower. H265 alone is a CPU hog and then you double up the resolution. That's a lot of bits to process. For test purposes set your download to 720p/H264 and see how fast it processes.
As far as the actual downloads on HULU, I am achieving greater than the 800 mbps that Comcast claims I'm set up for. I'm maxing out at 117 MBps on HULU. No other streamer on SF does that.
Cats4U
This was just an example screenshot. I don't download TV Shows in 4K. Only movies. Obviously the bigger the file, the longer it takes to process.
My observations are that at 1080p/H265, the processing is way longer than it was when 1080p/H265 was implemented.
I just did a test right now with a single episode of 9-1-1 Lone Star with v6.1.2.1 x64 and v6.1.1.0 x86. It's even possible the 32-bit version is slower than the 64-bit but i didn't want to uninstall 6.1.2.1. Different architectures can co-exist so it's great for comparison testing on the same hardware.
v6.1.2.1 Processing and Remuxing: 1 minute, 35 seconds.
v6.1.1.0 Processing and Remuxing: 1 minute, 1 second.
The resulting files are bit-for-bit identical.
This means v6.1.2.1 is a full
50% slower than v6.1.1.0.
I also noticed that 6.1.1.0 processes the video and audio separately but 6.1.2.1 does them simultaneously. I don't know if it's because they changed it in the recent versions or if it's because the 32-bit can only use 3GB of RAM so it's better to process separately as opposed to x64 that can use my full 16GB of RAM