XADMaster
XADMaster copied to clipboard
Slow extract to network drive @ OS X 10.9?
Originally reported on Google Code with ID 716
Jannejt:
Hi! I have a mounted network drive on my osx under /Volumes, but if I check from activity
monitor, unrarring is very slow, just about 4-6 megabytes/sec when it used to be like
20-30 before OSX update.
Same thing with unar from command line, but for example unrar can extract 20-30 megabytes/second
from command line.. (and unrarX) so problem is not in network or drives. Did apple
implement some sort of cache / temp stuff in os x 10.9 which makes it impossible for
unar to extract faster? Does unar have to extract it through some sort of local cache
or something which makes it terribly slow :(
hopefully this will be fixed soon :-)
IcyMidnight (IcyMidnight):
I have encountered this problem recently. All split rar archives take a really long time for The Unarchiver to extract from network drive to network drive.
E.g. I have 7 part rar archive that's about 325MB in size. The Archive Browser (Version 1.11.1 (109)) can extract it (network drive -> network drive) in about 20s. The Unarchiver (Version 3.11.1 (109)) takes about 10-15 minutes.
paracelsus:
Is this still a problem?
Jannejt:
just for a heads up, tried nfs, no go.. (finder crashes), but then configured afp server
(netatalk) on server side and now thru afp everything works, so problem is with osx
mavericks and samba, nothing to do with unarchiver.. just weird how old unrar 4.11
from command line transfers thru samba fast, but newer versions lag just like unarchiver
does.. but well, osx + samba.. what can you expect :D
Jannejt:
My problem is when extracting from local drive --> network drive. Command line version
(old version of unrar) extracts fine, but newer or archive browser writes only 5-6
mb/s to network drive (from local hdd)
leechtime:
I just tested this. unrar(5.0.1) ;unar (1.8.1) ,The Unarchiver (3.9.1), and The Archive
Browser (1.9.1) all extracted around the same time against rar files sitting on a network
drive. OSX 10.9.1.
paracelsus:
Haven't had a chance to test this yet, but I've been having issues with Chrome writing
really slowly to network drives on 10.9 too. I wonder if Apple did mess up something
with the network protocol for this update...