giorger 0 Posted January 7, 2020 Posted January 7, 2020 Hello :-) I am experiencing big delays when trying to open an image using either Emby Web App through Chrome or Emby Android App, even if all elements (Emby Server, Client Apps) are in the same local network. As an end user, i experience about 15 seconds of waiting to time to see the selected image, while it seems that the majority of the time is consumed from (quoting from server logs) "encoding image". I also noticed that even if i am requesting to view one picture, more than one are requested from server. Not sure if this is expected. What can i do in order to address this delay? Below are my server specs and also the respective emby server logs where: embyserver.txt containing the debug lines with the messages "Image encoding took..." lshw_output.txt containing the output from my linux server running Ubuntu 18.04.3 LTS (4.15.0-72-generic) iperf3.log containing iperf3 output checking the network connectivity between server & client Let me know if any further clarification would help here.
Luke 42077 Posted January 8, 2020 Posted January 8, 2020 Yes some of those times are long. Are the image files on really slow storage?
giorger 0 Posted January 8, 2020 Author Posted January 8, 2020 Hm, not sure on this. Technically speaking this is how it disk containing images is recognized from operating system - while commercially wise this is the disk https://www.amazon.com/Toshiba-Cache-6-0Gb-Internal-DT01ACA100/dp/B00HS7J0PO. Do you think that executing an "iotop" and pasting the results would be beneficial? disk:1 description: ATA Disk product: TOSHIBA DT01ACA1 vendor: Toshiba physical id: 0.1.0 bus info: scsi@3:0.1.0 logical name: /dev/sdc version: A750 serial: 27I8S5BFS size: 931GiB (1TB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=5 guid=3867ba4a-4bcf-43e0-8d57-fd1b7a434eb8 logicalsectorsize=512 sectorsize=4096 *-volume description: EXT4 volume vendor: Linux physical id: 1 bus info: scsi@3:0.1.0,1 logical name: /dev/sdc1 logical name: /media/1024_GB version: 1.0 serial: ae8bb52f-979c-4246-aa3d-015557c0be7a size: 931GiB capacity: 931GiB capabilities: journaled extended_attributes large_files huge_files dir_nlink recover 64bit extents ext4 ext2 initialized configuration: created=2017-05-19 23:41:17 filesystem=ext4 lastmountpoint=/media/1024_GB modified=2020-01-07 23:43:16 mount.fstype=ext4 mount.options=rw,relatime,errors=remount-ro,data=ordered mounted=2020-01-07 23:43:16 state=mounted
giorger 0 Posted January 8, 2020 Author Posted January 8, 2020 Please find attached 3 logs which were captured during a view operatiion of an image from Android client: vmstat.log is the output of the command vmstat -nt 1|tee vmstat.log top.log is the output of the command top -ibc|tee top.log iotop.log is the output of the command sudo iotop -obtq | tee -a iotop.log
Luke 42077 Posted January 11, 2020 Posted January 11, 2020 Ok, there's nothing obvious here unfortunately. For the next release we have updated our graphics library and that appears to have improved the performance, so there's a decent chance that will help with this.
giorger 0 Posted January 12, 2020 Author Posted January 12, 2020 Thank you Luke. Do we have an estimation more or less when new version will be released?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now