unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Akib Azmain Turja <akib@disroot.org>
Cc: 59641@debbugs.gnu.org
Subject: bug#59641: term is very slow
Date: Fri, 16 Dec 2022 20:57:41 +0200	[thread overview]
Message-ID: <83pmcji3bu.fsf@gnu.org> (raw)
In-Reply-To: <87zgbn2oep.fsf@disroot.org> (message from Akib Azmain Turja on Sat, 17 Dec 2022 00:29:02 +0600)

> From: Akib Azmain Turja <akib@disroot.org>
> Cc: 59641@debbugs.gnu.org
> Date: Sat, 17 Dec 2022 00:29:02 +0600
> 
> >> Here are the reports (attached), but don't seem to be human readable:
> >
> > Copy them from the display shown by profiler-report, after you expand it
> > completely.
> >
> > And the "cpu" profile is enough; the "mem" one doesn't add anything useful.
> 
> Sorry, I missed this reply.  I found this in debbugs.gnu.org.  :O
> 
> Here is the data:  (I didn't redo the steps, I just did
> 'M-x profiler-find-profile RET path/to/profile'.  ;)  )
> 
> --8<---------------cut here---------------start------------->8---
>         9397  95% - term-emulate-terminal
>         2710  27%  - term-handle-ansi-escape
>         1831  18%   - term-down
>            8   0%      term-move-columns
>          765   7%   - term-goto

Doesn't surprise me: most of the time is spent in term.el's business
logic, not in Emacs display primitives.

If you want to work on speeding up term.el, I suggest to start by
loading term.el (not term.elc) manually, and repeating the profiling
session.  That could tell you in more detail where are the hot sports
in those functions at the top of the profile.  Then some clever
optimization ideas are needed to make it significantly faster.

Thanks.





  reply	other threads:[~2022-12-16 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 20:00 bug#59641: term is very slow Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-27 20:31 ` Eli Zaretskii
2022-12-16 18:29   ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-16 18:57     ` Eli Zaretskii [this message]
2022-12-17 12:32       ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-17 15:47         ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pmcji3bu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59641@debbugs.gnu.org \
    --cc=akib@disroot.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).