public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: jik-cygwin@curl.com
Cc: cygwin@cygwin.com
Subject: Re: Optimizing away "ReadFile" calls when Make calls stat()
Date: Tue, 13 Feb 2001 11:35:00 -0000	[thread overview]
Message-ID: <200102131935.OAA09136@envy.delorie.com> (raw)
In-Reply-To: <20010213190131.14369.qmail@lizard.curl.com>

> I see three problems with that:
> 
> 1) The cache would have to be automatically invalidated whenever the
> 2) Many of our dependencies are checked over and over again in many
> 3) The implementation of such a global cache would be much more

I think an easier win would be to cache the bytes read within the
fhandler, not globally, so while each fhandler (i.e. open, stat,
whatnot) would still need to read the file itself, it would never need
to read it more than once.

If we still need more performance, perhaps a one-entry cache of the
most recent file accessed (and when) could be added, and ignored if
the data is more than, say, one second old.  Even if it were local to
one process, it would hit most of the usual cases (stat a file, alloc
a buffer, then open/read the file).

These should be easier wins (thus, more doable) than a global cache,
which NT should be providing itself as part of the disk cache
subsystem (for local drives, at least).  I don't think it's
appropriate for cygwin to go beyond this anyway - too many race
conditions arise.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2001-02-13 11:35 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-13 10:36 Jonathan Kamens
2001-02-13 10:56 ` Larry Hall (RFK Partners, Inc)
2001-02-13 11:01   ` jik-cygwin
2001-02-13 11:14     ` Larry Hall (RFK Partners, Inc)
2001-02-13 11:18       ` jik-cygwin
2001-02-13 11:26         ` Larry Hall (RFK Partners, Inc)
2001-02-13 11:35     ` DJ Delorie [this message]
2001-02-13 11:46       ` jik-cygwin
2001-02-13 11:54         ` DJ Delorie
2001-02-13 11:56           ` Jonathan Kamens
2001-02-13 12:06             ` DJ Delorie
2001-02-13 12:31             ` Larry Hall (RFK Partners, Inc)
2001-02-13 12:22           ` Christopher Faylor
2001-02-13 12:50             ` DJ Delorie
2001-02-14  0:12             ` Egor Duda
2001-02-14  0:17               ` Robert Collins
2001-02-15 11:47               ` Warren Young
2001-02-15 13:14                 ` Larry Hall (RFK Partners, Inc)
2001-02-15 14:17                   ` Charles S. Wilson
2001-02-16  1:34                     ` Warren Young
2001-02-16  8:07                       ` Larry Hall (RFK Partners, Inc)
2001-02-16  9:00                         ` Christopher Faylor
2001-02-15 14:17                   ` Christopher Faylor
2001-02-15 14:19                   ` Jonathan Kamens
2001-02-16  1:14                 ` Egor Duda
2001-02-16  1:29                   ` Warren Young
2001-02-13 15:28         ` Warren Young
2001-02-14  0:48           ` Lothan
2001-02-13 11:12   ` Earnie Boyd
2001-02-13 11:46   ` Christopher Faylor
2001-02-13 11:09 ` Earnie Boyd
2001-02-13 11:15   ` jik-cygwin
2001-02-13 11:48     ` Earnie Boyd
2001-02-13 11:54       ` jik-cygwin
2001-02-13 12:25         ` DJ Delorie
2001-02-13 12:50           ` Larry Hall (RFK Partners, Inc)
2001-02-13 12:51             ` DJ Delorie
2001-02-13 13:37             ` jfaith
2001-02-13 13:50             ` Mumit Khan
2001-02-13 14:13               ` DJ Delorie
2001-02-13 12:11       ` DJ Delorie
2001-02-13 11:24 ` Eric M. Monsler
2001-02-13 11:28   ` jik-cygwin
2001-02-13 12:04     ` Eric M. Monsler
2001-02-13 14:15 Puttkammer, Roman
2001-02-13 14:28 ` Christopher Faylor
2001-02-14  2:41 Bernard Dautrevaux
2001-02-14  4:46 Bernard Dautrevaux
2001-02-16  9:24 Bernard Dautrevaux
2001-02-16 10:17 ` Christopher Faylor

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=200102131935.OAA09136@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=cygwin@cygwin.com \
    --cc=jik-cygwin@curl.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 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).