From: Eli Zaretskii <eliz@gnu.org>
To: Karthik Chikmagalur <karthikchikmagalur@gmail.com>
Cc: jschmidt4gnu@vodafonemail.de, emacs-devel@gnu.org
Subject: Re: Understanding filter function calls
Date: Fri, 28 Jul 2023 08:47:21 +0300 [thread overview]
Message-ID: <834jlolh92.fsf@gnu.org> (raw)
In-Reply-To: <87mszh113e.fsf@gmail.com> (message from Karthik Chikmagalur on Thu, 27 Jul 2023 14:44:21 -0700)
> From: Karthik Chikmagalur <karthikchikmagalur@gmail.com>
> Date: Thu, 27 Jul 2023 14:44:21 -0700
>
> | dvisvgm version | Run in shell (s) | Run via Emacs (s) | Difference |
> |-----------------+------------------+-------------------+------------|
> | TeXLive 2022 | 1.427 | 1.786 | 25% |
> | TeXLive 2023 | 1.481 | 2.202 | 48% |
>
> The variances are small and have been omitted. So TeXLive 2023's
> dvisvgm is about 48% slower when called from Emacs because it's waiting
> on Emacs to pick up the process output.
I think it isn't that dvisvgm is waiting for Emacs, it's that the
whole process of reading output by Emacs and processing that output
takes longer.
> Using a larger stream buffer (if possible) should fix this issue.
You already tried that, AFAIU, and it didn't help.
next prev parent reply other threads:[~2023-07-28 5:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 5:46 Understanding filter function calls Karthik Chikmagalur
2023-07-24 20:57 ` Jens Schmidt
2023-07-27 21:08 ` Karthik Chikmagalur
2023-07-27 21:44 ` Karthik Chikmagalur
2023-07-28 5:47 ` Eli Zaretskii [this message]
2023-07-28 5:44 ` Eli Zaretskii
2023-07-28 21:42 ` Karthik Chikmagalur
2023-07-29 6:02 ` Eli Zaretskii
2023-07-29 22:16 ` Karthik Chikmagalur
2023-07-30 5:14 ` Eli Zaretskii
2023-07-28 7:54 ` Ihor Radchenko
2023-07-28 21:51 ` Karthik Chikmagalur
2023-07-29 6:04 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2024-04-18 3:52 Karthik Chikmagalur
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=834jlolh92.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
--cc=karthikchikmagalur@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 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).