From: chad <yandros@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: "Winston Carlile via Emacs development discussions."
<emacs-devel@gnu.org>, Winston Carlile <winstonc@google.com>
Subject: Re: Making elp.el behave like a real profiler
Date: Wed, 17 Aug 2022 14:33:10 -0400 [thread overview]
Message-ID: <CAO2hHWb+OKRhwffX=Z0EX9KbA3ZGwUj9=Nn=tJQ6bMnX0vXw2w@mail.gmail.com> (raw)
In-Reply-To: <87v8qr2pof.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
>
> In my experience, most time in Tramp is spent on wire. That is, sending
> commands to the remote shell, and reading the command's output. Compared
> with this, time spent in Elisp is not so important (although any
> optimization will be appreciated as well).
Based on this, I wonder how useful/difficult it would be to add a sort of
"ping timer" to buffers that make regular use of remote commands, measuring
the delta between just before the most recent send and the following
(assuming no interleaving) recv. With that raw data, it should be
relatively easy to add things like a moving average and/or an alert for
sudden spikes.
Would this be more likely to result in a useful diagnostic or a computed
indicator that slow things are slow?
~Chad
[-- Attachment #2: Type: text/html, Size: 996 bytes --]
prev parent reply other threads:[~2022-08-17 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 19:22 Making elp.el behave like a real profiler Winston Carlile via Emacs development discussions.
2022-08-16 15:27 ` Stefan Monnier
2022-08-16 15:48 ` Stefan Kangas
2022-08-17 9:18 ` Michael Albinus
2022-08-17 18:33 ` chad [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
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='CAO2hHWb+OKRhwffX=Z0EX9KbA3ZGwUj9=Nn=tJQ6bMnX0vXw2w@mail.gmail.com' \
--to=yandros@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=winstonc@google.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 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).