all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bogdan Sirb <bogdans91@yahoo.com>
Cc: 24143-done@debbugs.gnu.org
Subject: bug#24143: 25.1; Windows performace of process-send-string
Date: Thu, 04 Aug 2016 17:57:47 +0300	[thread overview]
Message-ID: <83zioslgyc.fsf@gnu.org> (raw)
In-Reply-To: <333655155.11634740.1470310820582.JavaMail.yahoo@mail.yahoo.com> (message from Bogdan Sirb on Thu, 4 Aug 2016 11:40:20 +0000 (UTC))

tags 24143 + notabug
thanks

> Date: Thu, 4 Aug 2016 11:40:20 +0000 (UTC)
> From: Bogdan Sirb <bogdans91@yahoo.com>
> Cc: "24143@debbugs.gnu.org" <24143@debbugs.gnu.org>
> 
> Emacs 24.5 was the one found in the repository of msys2 found
> https://msys2.github.io/ I also tried the standard one found on emacs website
> and the results were the same.

That doesn't tell how it was compiled.  My idea was that when
comparing performance of two versions, one should make sure both
builds used similar compilation switches, otherwise you could see all
kinds of strange disparities.

> But doing a (setq w32-pipe-buffer-size (* 10 4096)) fixed the problem.

Great, so I'm closing this bug.

> Now I have the following:
> 
> * emacs 24.5: 0.037496
> * emacs 25.1: 0.040418
> 
> But, if I'm doing a (setq w32-pipe-buffer-size (point-max)) to send the whole
> file at once once, I get a stunning 0.0010007 per call.
> 
> Is there any implications to doing this ?

It depends on what program is on the other end of the pipe.  Some
programs don't like large writes down the pipe.  See bug#22344, where
such large writes caused a catastrophic failure.  Emacs prefers to err
on the safe side by default, and leave any fine-tuning of the pipe
size to applications that need it.

Thanks.





      reply	other threads:[~2016-08-04 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <601571075.10415562.1470227331338.JavaMail.yahoo.ref@mail.yahoo.com>
2016-08-03 12:28 ` bug#24143: 25.1; Windows performace of process-send-string Bogdan Sirb
2016-08-03 16:37   ` Eli Zaretskii
2016-08-04 11:40     ` Bogdan Sirb
2016-08-04 14:57       ` 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=83zioslgyc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24143-done@debbugs.gnu.org \
    --cc=bogdans91@yahoo.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.