From: Eli Zaretskii <eliz@gnu.org>
To: John Mastro <john.b.mastro@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Default compiler optimization level for building dev sources
Date: Fri, 22 Apr 2016 23:41:35 +0300 [thread overview]
Message-ID: <83fuud5qbk.fsf@gnu.org> (raw)
In-Reply-To: <CAOj2CQShusJBKe6bm4JJQeU+PVAytXQrUj_78uxNcir3ewqMng@mail.gmail.com> (message from John Mastro on Fri, 22 Apr 2016 13:25:13 -0700)
> From: John Mastro <john.b.mastro@gmail.com>
> Date: Fri, 22 Apr 2016 13:25:13 -0700
>
> Magit has some useful notes regarding performance[1], including for
> Windows specifically.
>
> (I don't mean to comment on whether the performance problems are with
> Emacs and/or Magit, only to point it out in case you haven't seen it).
>
> [1]: https://magit.vc/manual/magit/Performance.html
When was that last updated/verified? I think the information there is
mostly outdated. E.g., the stackoverflow question and advice refers
to Git 1.7.x, and definitely describes a broken setup ("cd" taking 8
to 25 sec? come on, be serious!).
The only factor I'm aware of for slow startup of Git on Windows is due
to MSYS Bash and other MSYS commands that are run by those Git
commands that are implemented as shell or Perl scripts. MSYS is a
fork of Cygwin, which is known for this issue (emulating 'fork' on
Windows is expensive). Git commands that don't invoke Bash or Perl
should be fast enough on Windows, AFAIK.
prev parent reply other threads:[~2016-04-22 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 14:17 Default compiler optimization level for building dev sources Óscar Fuentes
2016-04-22 14:40 ` Eli Zaretskii
2016-04-22 15:00 ` Óscar Fuentes
2016-04-22 17:56 ` John Wiegley
2016-04-22 18:40 ` Eli Zaretskii
2016-04-22 18:53 ` Andreas Schwab
2016-04-22 20:18 ` Óscar Fuentes
2016-04-22 20:25 ` John Mastro
2016-04-22 20:41 ` 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
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=83fuud5qbk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=john.b.mastro@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).