Page 1 of 1
FileBot very long since DSM 6 upgrade
Posted: 06 Apr 2016, 15:50
by migeon
Hello,
I use the amc script in order to move and rename my shows and films on my Synology NAS (DS414).
Since I upgraded the DSM to 6.0 FileBot execution is very long (almost 10mins to move a single movie).
Here is how I use FileBot:
Code: Select all
/usr/local/bin/filebot -script 'fn:amc' /volume1/download --output /volume1/ \
-non-strict --conflict auto --log all --lang en \
--def 'music=y' 'unsorted=y' 'subtitles=eng' 'deleteAfterExtract=y' 'excludeList=/volume1/download/.excludes' \
"seriesFormat=video/series/{n}/Season {s}/{n.space('.')}.{S00E00}.{vf}.{source}.{vc.replaceAll('AVC', 'x264')}{'-'+group}{'.'+lang}" \
"movieFormat=video/films/{n.space('.')}.{vf}{'.'+source}.{vc.replaceAll('AVC', 'x264')}{'-'+group}{'.'+lang}" \
"musicFormat=music/{albumartist}/{album}/{t}" \
"exec=synoindex -a \"{file}\""
Here is the result of filebot -script fn:sysinfo:
Code: Select all
filebot -script fn:sysinfo
FileBot 4.6.1 (r3315)
JNA Native: 4.0.1
MediaInfo: MediaInfoLib - v0.7.73
Apache Commons VFS: [zip, ftps, rar, ftp, tar, tgz, tbz2, sftp]
Chromaprint: fpcalc version 1.2.0 (/usr/local/chromaprint/bin/fpcalc)
Extended Attributes: OK
Groovy Engine: 2.4.5
JRE: OpenJDK Runtime Environment 1.8.0_60 (headless)
JVM: 32-bit OpenJDK Zero VM
CPU/MEM: 2 Core / 489 MB Max Memory / 12 MB Used Memory
OS: Linux (arm)
Package: SPK
Data: /volume1/@appstore/filebot/data/admin
uname: Linux DiskStation 3.2.40 #7321 SMP Wed Mar 23 11:46:12 CST 2016 armv7l GNU/Linux synology_armadaxp_ds414
Done ヾ(＠⌒ー⌒＠)ノ
Any idea would be appreciated
Regards,
Re: FileBot very long since DSM 6 upgrade
Posted: 02 May 2016, 13:31
by maxoudela
Hi,
Have you found some answers?
When I run a simple task, I also feel like FileBot is taking forever to do a simple task..
Re: FileBot very long since DSM 6 upgrade
Posted: 02 May 2016, 16:24
by rednoah
Using Oracle Java is highly recommended.
The 32-bit OpenJDK Zero VM on ARM doesn't do any JITing, AFAIK. I'd expect it to be very slow.
Re: FileBot very long since DSM 6 upgrade
Posted: 04 May 2016, 10:06
by maxoudela
On my side, here is what I have, I need to wait one minute before sysInfo print something on screen, is it normal?
Code: Select all
FileBot 4.7 (r3923)
JNA Native: 4.0.1
MediaInfo: java.lang.UnsatisfiedLinkError: Unable to load library 'zen': Native library (linux-arm/libzen.so) not found in resource path ([file:/volume1/@appsto re/filebot/FileBot.jar])
Apache Commons VFS: [zip, ftps, rar, ftp, tar, tgz, tbz2, sftp]
Chromaprint: java.io.IOException: Cannot run program "/usr/local/chromaprint/bin /fpcalc": error=2, No such file or directory
Extended Attributes: OK
Groovy Engine: 2.4.6
JRE: Java(TM) SE Runtime Environment 1.8.0_91 (headless)
JVM: 32-bit Java HotSpot(TM) Client VM
CPU/MEM: 1 Core / 92 MB Max Memory / 9 MB Used Memory
OS: Linux (arm)
Package: SPK
Data: /volume1/@appstore/filebot/data/master
uname: Linux MaxoudelaServer 3.2.40 #7321 Wed Mar 23 11:48:58 CST 2016 armv7l GN U/Linux synology_armada370_ds115j
Done ヾ(＠⌒ー⌒＠)ノ
Re: FileBot very long since DSM 6 upgrade
Posted: 04 May 2016, 10:58
by rednoah
On underpowered devices you might run into certain bottlenecks. Especially older ARM devices with little RAM.
Here's what I get on my DS213J:
Code: Select all
$ time filebot -script fn:sysinfo | grep uname
Code: Select all
uname: Linux DiskStation 3.2.40 #7321 Wed Mar 23 11:48:58 CST 2016 armv7l GNU/Linux synology_armada370_213j
real 0m19.233s
user 0m18.010s
sys 0m0.720s
Also, the sysinfo script does check for updates, so there might be slow network requests making it useless for any kind of benchmarking. Doing nothing but a simple println will give you a better idea as to how fast/slow it really is:
Code: Select all
$ time filebot -script "g:println now"
Wed May 04 18:57:08 CST 2016
Done ヾ(＠⌒ー⌒＠)ノ
real 0m7.096s
user 0m6.600s
sys 0m0.320s
Re: FileBot very long since DSM 6 upgrade
Posted: 04 May 2016, 15:52
by maxoudela
Here is what I have
Code: Select all
master@MaxoudelaServer:~$ time filebot -script "g:println now"
Wed May 04 17:52:00 CEST 2016
Done ヾ(＠⌒ー⌒＠)ノ
real 0m12.666s
user 0m8.750s
sys 0m0.680s
So It's kinda like you.. Nothing to be alarmed in my case then I believe.
Thanks
Re: FileBot very long since DSM 6 upgrade
Posted: 06 May 2016, 18:23
by migeon
Re-installed Java through your "unofficial java installer" and it works fine now.
Re: FileBot very long since DSM 6 upgrade
Posted: 02 Nov 2016, 16:45
by ArTi
any idea why Filebot is very slow on my NAS ?
Code: Select all
Linux 3.10.77 #8451 SMP Wed Aug 17 05:13:40 CST 2016 x86_64 GNU/Linux synology_braswell_216+II
real 1m14.154s
user 0m16.378s
sys 0m0.802s
and another report :
Code: Select all
FileBot 4.7.2 (r4178)
JNA Native: 4.0.1
MediaInfo: net.filebot.mediainfo.MediaInfoException: Unable to load amd64 (64-bit) native library libmediainfo.so: Unable to load library 'zen': Native library (linux-x86-64/libzen.so) not found in resource path ([file:/volume1/@appstore/filebot/FileBot.jar])
Apache Commons VFS: [zip, rar]
Chromaprint: java.io.IOException: Cannot run program "/usr/local/chromaprint/bin/fpcalc": error=2, No such file or directory
Extended Attributes: OK
Script Bundle: 2016-10-31 (r448)
Groovy: 2.4.7
JRE: Java(TM) SE Runtime Environment 1.8.0_101 (headless)
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM
CPU/MEM: 2 Core / 614 MB Max Memory / 18 MB Used Memory
OS: Linux (amd64)
Package: SPK
Data: /volume1/@appstore/filebot/data/admin
uname: Linux NAS-GDU 3.10.77 #8451 SMP Wed Aug 17 05:13:40 CST 2016 x86_64 GNU/Linux synology_braswell_216+II
Done ヾ(＠⌒ー⌒＠)ノ
Re: FileBot very long since DSM 6 upgrade
Posted: 02 Nov 2016, 20:56
by rednoah
Run this command and post the output:
Code: Select all
time filebot -script "g:println now"
Re: FileBot very long since DSM 6 upgrade
Posted: 06 Jan 2020, 16:43
by ArTi
here is the answer of : time filebot -script "g:println now" :
Code: Select all
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
pwd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
pwd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Mon Jan 06 17:43:24 CET 2020
Done ヾ(＠⌒ー⌒＠)ノ
real 0m5.256s
user 0m4.640s
sys 0m0.390s