From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 40516-done@debbugs.gnu.org
Subject: bug#40516: 28.0.50; Delays with copy/rename after 10 hours emacs uptime
Date: Thu, 09 Apr 2020 14:25:59 +0300 [thread overview]
Message-ID: <83pncgoq7s.fsf@gnu.org> (raw)
In-Reply-To: <20200409082428.GI9475@protected.rcdrun.com> (message from Jean Louis on Thu, 9 Apr 2020 11:24:29 +0300)
> Date: Thu, 9 Apr 2020 11:24:29 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: 40516@debbugs.gnu.org
>
> > > Then I have observed that copies and renames are slower and slower,
> > > incredibly slow. Deleting files became very slow. If I would do it in
> > > the shell it would be very fast.
> >
> > Do you have gc-cons-threshold set to a very high value, per chance?
>
> Its value is 10000000
> Original value was 800000
>
> Is that maybe the case? I will reset it.
It could be. I suggest to set garbage-collection-messages non-nil,
and see if Emacs says "Garbage collecting..." whenever you see the
delays.
In general, 10MB is quite high a setting, yes.
> > In any case, when this happens next time, profile Emacs with "M-x
> > profiler-start", then post the resulting profile, completely expanded,
> > here. Without that data, it is hard to do anything useful about this
> > bug report, as it gives no clue about the possible reason(s). FWIW,
> > my Emacs sessions typically run for many weeks without any tangible
> > degradation in the time it takes to copy or move files.
>
> Thank you, then for now it can be closed. I can re-open if I see
> problem taking place.
Closing.
prev parent reply other threads:[~2020-04-09 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 4:43 bug#40516: 28.0.50; Delays with copy/rename after 10 hours emacs uptime Jean Louis
2020-04-09 7:00 ` Eli Zaretskii
2020-04-09 8:24 ` Jean Louis
2020-04-09 11:25 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pncgoq7s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40516-done@debbugs.gnu.org \
--cc=bugs@gnu.support \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.