all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: uyennhi.qm@gmail.com, 42911@debbugs.gnu.org
Subject: bug#42911: 28.0.50; write_region sometimes extremely very slow
Date: Tue, 25 Aug 2020 19:19:02 +0300	[thread overview]
Message-ID: <83pn7e4s22.fsf@gnu.org> (raw)
In-Reply-To: <874koqsoe6.fsf@gmail.com> (message from Tino Calancha on Tue, 25 Aug 2020 18:04:17 +0200)

> From: Tino Calancha <tino.calancha@gmail.com>
> Cc: uyennhi.qm@gmail.com,  42911@debbugs.gnu.org
> Date: Tue, 25 Aug 2020 18:04:17 +0200
> 
> > Did you check that GC doesn't kick in when the "slow" saving happens?
> `benchmark-run` lets you know teh number of GC and the time used by them
> while running the form.  The reported slowliness was happening even
> without GC.
> I was curious if someone runnning opensuse Tumbleweed was seeing something similar.
> 
> I suspect this might be a problem of my OS (probably it was under heavy stress).
> Now I am in vacation, and the computer seems more relax (same like me).  I have also
> upgraded the OS and got a new kernel.
> 
> The following is data right now running this:
> emacs -Q /tmp/save-slow-buffer.txt
> ;; evaluate the following key binding:
> 
> (global-set-key (kbd "<f5>") (lambda () (interactive) (print
> (benchmark-run nil (save-buffer)) (current-buffer))))
> 
> ;; now push <f5> slowly several times
> ;; Still seems a bit slow sometimes (~0.1 s) but it is acceptable for my needs:

If it isn't GC, then my suggestion would be to run Emacs under 'perf'
and see what the profile tells us.





  reply	other threads:[~2020-08-25 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18  9:46 bug#42911: 28.0.50; write_region sometimes extremely very slow Tino Calancha
2020-08-18 10:44 ` Eli Zaretskii
2020-08-25 16:04   ` Tino Calancha
2020-08-25 16:19     ` Eli Zaretskii [this message]
2021-07-23 20:13 ` Tino Calancha

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=83pn7e4s22.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=42911@debbugs.gnu.org \
    --cc=tino.calancha@gmail.com \
    --cc=uyennhi.qm@gmail.com \
    /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.