unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eighty Megabytes <emacsuser@freemail.hu>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Does emacs cache something on windows when invoking call-process?
Date: Tue,  9 Jul 2019 22:54:55 +0200 (CEST)	[thread overview]
Message-ID: <AxrVTQ.rWhJj0vvlyx9.bk65Mt7ZMQrc3LWBpl3j@freemail.hu> (raw)

> What kind of program is ripgrep?  Is it per chance a Cywgin or MSYS2
> executable?  If so, perhaps the time you see is spent loading the
> Cygwin/MSYS2 DLL.

I ran the emacs test about 5 seconds after the command prompt test.
so I don't think windows would forget about the already loaded
DLLs in a such a short time.

I tried to trace the process and it seems to me when the search is run
via emacs then windows defender checks every source file read by ripgrep
and I assume this slows down the search.

When tracing an invocation via the command prompt then there are no checking
of source files, so it looks like windows defender thinks emacs is a suspicious
program or maybe it considers the invocation of cmdproxy.exe  suspicious.

With windows defender turned off for the given source directory the delay
practically disappears.


             reply	other threads:[~2019-07-09 20:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09 20:54 Eighty Megabytes [this message]
2019-07-09 21:30 ` Does emacs cache something on windows when invoking call-process? Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2019-07-10 21:10 Eighty Megabytes
2019-07-10  8:34 Eighty Megabytes
2019-07-10  5:31 Eighty Megabytes
2019-07-10  6:08 ` ISHIKAWA,chiaki
2019-07-10 14:33 ` Eli Zaretskii
2019-07-09 17:08 Eighty Megabytes
2019-07-09 17:27 ` Eli Zaretskii
2019-07-09 15:58 Eighty Megabytes
2019-07-09 16:16 ` Eli Zaretskii
2019-07-09 14:03 Eighty Megabytes
2019-07-09 15:27 ` 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=AxrVTQ.rWhJj0vvlyx9.bk65Mt7ZMQrc3LWBpl3j@freemail.hu \
    --to=emacsuser@freemail.hu \
    --cc=help-gnu-emacs@gnu.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.
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).