2025-06-06, 11:51 AM
(This post was last modified: 2025-06-06, 11:58 AM by bitstream. Edited 2 times in total.)
You first need to find out if its a client or a server problem. Second thing then is to find out if it's a JF frontend or backend problem. This said:
1) Is it the same from different client computer with different client apps?
2) Is it only slow with media streaming or also to navigate the UI?
3) Is it only the GUI being slow or is it also the media scanning and so on?
4) Have you check server load on the server running JF? Also look for processes other than JF, i.e. ffmpeg.
5) Have you tried to turn off https and any proxies in front of JF and directly access JF?
General remark: N100 is a 4 core system with E-Cores only. It's great for general file serving, however when it comes to tasks where encoding and transcoding is needed, it will consume significant cpu power and as it's not very powerful in terms of media processing, it will take time. On top of this, JF is built on .Net and needs rather more than lesser ressources.
1) Is it the same from different client computer with different client apps?
2) Is it only slow with media streaming or also to navigate the UI?
3) Is it only the GUI being slow or is it also the media scanning and so on?
4) Have you check server load on the server running JF? Also look for processes other than JF, i.e. ffmpeg.
5) Have you tried to turn off https and any proxies in front of JF and directly access JF?
General remark: N100 is a 4 core system with E-Cores only. It's great for general file serving, however when it comes to tasks where encoding and transcoding is needed, it will consume significant cpu power and as it's not very powerful in terms of media processing, it will take time. On top of this, JF is built on .Net and needs rather more than lesser ressources.