GNU bug report logs - #28227
26.0.50; Tramp tests are slow

Previous Next

Package: emacs;

Reported by: Gemini Lasswell <gazally <at> runbox.com>

Date: Thu, 24 Aug 2017 21:05:01 UTC

Severity: normal

Found in version 26.0.50

Done: Gemini Lasswell <gazally <at> runbox.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Gemini Lasswell <gazally <at> runbox.com>
Subject: bug#28227: closed (Re: bug#28227: 26.0.50; Tramp tests are slow)
Date: Sat, 09 Sep 2017 16:29:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#28227: 26.0.50; Tramp tests are slow

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 28227 <at> debbugs.gnu.org.

-- 
28227: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=28227
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Gemini Lasswell <gazally <at> runbox.com>
To: 28227-done <at> debbugs.gnu.org
Cc: Michael Albinus <michael.albinus <at> gmx.de>, npostavs <at> users.sourceforge.net
Subject: Re: bug#28227: 26.0.50; Tramp tests are slow
Date: Sat, 09 Sep 2017 09:27:25 -0700
Michael Albinus writes:

> Gemini Lasswell <gazally <at> runbox.com> writes:
>> Here's a new version of the patch which incorporates your suggestions:
>
> LGTM, thanks!

Pushed to master.

[Message part 3 (message/rfc822, inline)]
From: Gemini Lasswell <gazally <at> runbox.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 26.0.50; Tramp tests are slow
Date: Thu, 24 Aug 2017 14:03:32 -0700
[Message part 4 (text/plain, inline)]
The Tramp tests are the slowest tests in Emacs's test suite, even when
they aren't set up to access a remote machine.

After a little investigation I think the cause of the slowness is
excessive memory allocation. I modified ert-run-tests to print
memory statistics after each test and found that tramp-tests.el, which
takes 100 seconds to run on my machine, is spending 39 seconds doing
garbage collection, and by the end of the test run has allocated and
freed 27 million strings.

Here is a log file with memory statistics:

[tramp-tests.log (text/plain, attachment)]
[Message part 6 (text/plain, inline)]
And here are the messages I added to ert-run-test's loop:

(message "GC: %s" (garbage-collect))
(message "GC count: %s time: %s" gcs-done gc-elapsed)
(message "Memory-use-counts: %s" (memory-use-counts))

This bug report was last modified 7 years and 338 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.