2024-02-21, 04:04 PM
(This post was last modified: 2024-02-21, 04:10 PM by Marco2G. Edited 3 times in total.)
This is an Ubuntu 22.04 VM with two CPU cores of E5-2650 v2 @ 2.60GHz, 4GB RAM and a Quadro P400 for hardware acceleration.
I have this issue both on two independent computers running the web client in Firefox and on my Android through the Android client. It's the same on both.
Edit: Just tried T2 in 4k. Started inside 5 seconds. So it isn't a question of file size or network latency.
Which brings me to describing my setup a bit more. I have a frankenserver build that runs ESXi on which I am running TrueNAS in a VM. I have PCI passthroughed an HBA so the trueNAS can work the 12ish spindles in ZFS. I also have three NVMe gumsticks in another ZFS pool. The Jellyfin VM runs on that. The Media is mounted into Jellyfin via NFS. Since both it and the TrueNAS VM run on the same hypervisor, I'd say network traffic should remain on the virtual switch. Both for the Jellyfin's iSCSI NVMe datastore and the NFS mount for the media. If it doesn't, the Machine is connected to the physical switch via 10G fiber.
I have this issue both on two independent computers running the web client in Firefox and on my Android through the Android client. It's the same on both.
Edit: Just tried T2 in 4k. Started inside 5 seconds. So it isn't a question of file size or network latency.
Which brings me to describing my setup a bit more. I have a frankenserver build that runs ESXi on which I am running TrueNAS in a VM. I have PCI passthroughed an HBA so the trueNAS can work the 12ish spindles in ZFS. I also have three NVMe gumsticks in another ZFS pool. The Jellyfin VM runs on that. The Media is mounted into Jellyfin via NFS. Since both it and the TrueNAS VM run on the same hypervisor, I'd say network traffic should remain on the virtual switch. Both for the Jellyfin's iSCSI NVMe datastore and the NFS mount for the media. If it doesn't, the Machine is connected to the physical switch via 10G fiber.