Am 22.10.2013 16:49, schrieb Sebastian Schuberth: > On Tue, Oct 22, 2013 at 4:30 PM, Karsten Blees <karsten.blees@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html