git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff Hostetler <git@jeffhostetler.com>
To: Tao Klerks <tao@klerks.biz>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git <git@vger.kernel.org>,
	Jeff Hostetler <jeffhost@microsoft.com>,
	Derrick Stolee <dstolee@microsoft.com>
Subject: Re: Windows: core.useBuiltinFSMonitor without core.untrackedcache - performance hazard?
Date: Thu, 24 Jun 2021 09:10:35 -0400	[thread overview]
Message-ID: <596386e9-f9bf-c465-ec5e-dcf4356b6194@jeffhostetler.com> (raw)
In-Reply-To: <CAPMMpojKMZmorKPgMASkHsvKcQTaaGyWURsgDS+KTGVeuBh1ww@mail.gmail.com>



On 6/24/21 1:25 AM, Tao Klerks wrote:
> Hi Jeff,
> 
> On Mon, Jun 21, 2021 at 8:41 PM Jeff Hostetler <git@jeffhostetler.com> wrote:
>> We're currently looking at a problem that we believe is in the
>> untracked-cache code.  This is causing some of our Scalar tests
>> to fail on Windows when the untracked-cache is turned on.  This
>> is independent of whether FSMonitor or FSCache is turned on.
>> We're still tracking this down.
>>
>> And yes, the best possible solution is to turn on FSMonitor *and*
>> the untracked-cache, so that the "untracked" status code doesn't
>> have to do anything.  So I want to look at tracking down the above
>> problem before doing anything else.
> 
> I got a bit excited about a possible clean path forward to getting
> -uall to work well with untracked cache, and submitted a patch along
> those lines, but rereading the above I should probably have been a
> little more patient.
> 
> Is there anything "we" can do to see/understand the
> scalar-test-suite-error you describe above, or is this
> microsoft-internal?
> 
> Thanks
> Tao
> 

Thanks for looking into this.  The untracked-cache code is pretty
dense and having another set of eyes is good.  I apologize that I'm
still working thru the backlog from my vacation and haven't gotten
to spend any "quality" time with the untracked-cache code yet, so
I need to do some homework and study the questions/issues that you've
found so far. (Thanks again)

All of our work is done in the open, so yes you should be able to
see what we're doing and the errors that we're getting.

The source for our Scalar functional tests is in:
https://github.com/microsoft/scalar

My test branch 'test-no-fscache' is in my personal development fork:
https://github.com/jeffhostetler/git

I have a PR against microsoft/git (a fork of git-for-windows
which is a fork of core git) which turns off a bunch of things
to try to isolate the failures:
https://github.com/microsoft/git/pull/383

Output for a recent run can be seen here:
https://github.com/microsoft/git/pull/383/checks?check_run_id=2884524819

Let us know if you have questions.
Jeff

      reply	other threads:[~2021-06-24 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 10:24 Windows: core.useBuiltinFSMonitor without core.untrackedcache - performance hazard? Tao Klerks
2021-06-11  9:49 ` Johannes Schindelin
2021-06-21 12:50   ` Tao Klerks
2021-06-21 18:41     ` Jeff Hostetler
2021-06-21 20:52       ` Tao Klerks
2021-06-24 18:51         ` Tao Klerks
2021-06-24  5:25       ` Tao Klerks
2021-06-24 13:10         ` Jeff Hostetler [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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=596386e9-f9bf-c465-ec5e-dcf4356b6194@jeffhostetler.com \
    --to=git@jeffhostetler.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dstolee@microsoft.com \
    --cc=git@vger.kernel.org \
    --cc=jeffhost@microsoft.com \
    --cc=tao@klerks.biz \
    /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://80x24.org/mirrors/git.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).