GNU bug report logs -
#36940
tests slowness and failure after recent Tramp changes
Previous Next
Reported by: Paul Eggert <eggert <at> cs.ucla.edu>
Date: Tue, 6 Aug 2019 00:29:02 UTC
Severity: normal
Done: Paul Eggert <eggert <at> cs.ucla.edu>
Bug is archived. No further changes may be made.
Full log
Message #35 received at 36940 <at> debbugs.gnu.org (full text, mbox):
Paul Eggert <eggert <at> cs.ucla.edu> writes:
Hi Paul,
> Thanks, it does fix the failure. However, the test is still quite a
> bit slower for me than you even when I invoke it the way you suggest,
> as it takes 108 seconds for me compared to 30 seconds for you. The
> four slowest tests are:
>
> passed 37/47 tramp-test35-remote-path (25.712913 sec)
> passed 42/47 tramp-test41-utf8 (14.036743 sec)
> passed 17/47 tramp-test12-rename-file (8.772317 sec)
> passed 16/47 tramp-test11-copy-file (7.754914 sec)
My machine is about 10 years old (Ubuntu 19.04, Intel Core2 Duo T95,
4GB). It runs today
passed 37/47 tramp-test35-remote-path (4.826182 sec)
passed 42/47 tramp-test41-utf8 (2.885723 sec)
passed 17/47 tramp-test12-rename-file (1.725029 sec)
passed 16/47 tramp-test11-copy-file (1.437843 sec)
But experience has shown, that it easily doubles or triples the time if
there are parallel tasks. It would need more debugging on your machine
in order to understand, where the time is spent.
Best regards, Michael.
This bug report was last modified 5 years and 326 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.