From: Karsten Blees <karsten.blees@gmail.com>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: pro-logic <pro-logic@optusnet.com.au>,
msysGit Mailinglist <msysgit@googlegroups.com>,
Git Mailing List <git@vger.kernel.org>,
szager@google.com
Subject: Re: Re: Windows performance / threading file access
Date: Tue, 22 Oct 2013 17:40:08 +0200 [thread overview]
Message-ID: <52669C58.4020801@gmail.com> (raw)
In-Reply-To: <CAHGBnuOVpMU6wBmjesYK7qWWpKPyCFhmDcWny7MN5nM4zYFjDA@mail.gmail.com>
Am 22.10.2013 16:49, schrieb Sebastian Schuberth:
> On Tue, Oct 22, 2013 at 4:30 PM, Karsten Blees <karsten.blees@gmail.com> wrote:
>
>>>> Could you post details about your test setup? Are you still using
>>>> WebKit for your tests?
>>> I'm on Win7 x64, Core i5 M560, WD 7200 Laptop HDD, NTSF, no virus
>>> scanner, truecrypt, no defragger.
>>>
>>
>> OK, so truecrypt and luafv may screw things up for you (according to my measurements, luafv roughly doubles lstat times on C:).
>
> Aren't we disabling UAC / LUAFV on a per-executable basis using
> manifests? At least the blog article at [1] suggests that we are in
> fact doing it the right way using our script to genera the manifests
> [2].
>
> Oh but wait, we're not generating a manifest for git.exe itself, only
> for executables that contain "setup", "install", "update", "patch"
> etc. So maybe having a manifest for git.exe, too, would improve
> performance?
>
Even with UAC disabled in control panel, the luafv.sys driver slows things down on C: (no impact on non-system drives). Procmon shows that with disabled luafv, GetFileAttributesEx is a single FASTIO call. With luafv running, FASTIO fails and is followed by three IRP calls (open, query, close).
I haven't tried with UAC enabled, or if disabling virtualization for git.exe has an impact.
Karsten
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
prev parent reply other threads:[~2013-10-22 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 18:18 Windows performance / threading file access Stefan Zager
2013-10-10 20:19 ` Sebastian Schuberth
2013-10-11 0:51 ` Karsten Blees
2013-10-11 5:28 ` Stefan Zager
2013-10-11 5:35 ` Stefan Zager
2013-10-11 5:48 ` Duy Nguyen
2013-10-15 22:22 ` pro-logic
2013-10-17 16:50 ` Karsten Blees
2013-10-21 22:58 ` pro-logic
2013-10-22 14:30 ` Karsten Blees
2013-10-22 14:49 ` Sebastian Schuberth
2013-10-22 15:40 ` Karsten Blees [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=52669C58.4020801@gmail.com \
--to=karsten.blees@gmail.com \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
--cc=pro-logic@optusnet.com.au \
--cc=sschuberth@gmail.com \
--cc=szager@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.
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.