public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: A Simple Real World Benchmark for cygwin
Date: Mon, 02 Sep 2002 15:02:00 -0000	[thread overview]
Message-ID: <20020902220234.GA22844@redhat.com> (raw)
In-Reply-To: <CHEDKHJJDLOCCOFLMGEAOEHMCLAA.dvasaru@broadpark.no>

On Mon, Sep 02, 2002 at 11:34:11PM +0200, Dan Vasaru wrote:
>cgf> or investigate the code and offer ways to speed it up.
>
>Here's a potential speedup for non-NTFS symlinks:
>
>The check_shortcut function in shortcut.c calls CoInitialize/CoUninitialize
>for *every* .LNK it needs to check on non EA filesystems.
>
>I ran a small test on my computer, calling check_shortcut 1000 times.
>When I moved the calls to CoInitialze/CoUnitialize outside the
>check_shortcut function, the function throughput increased from 59 calls/sec
>to 960 calls/sec.
>
>As it turns out, CoInit...CoUninit costs up to 20 msecs on my system.
>
>So my suggestion is that the CoInit../CoUnit... calls be moved to another
>spot, to be called once per thread.
>
>
>Dan.
>
>PS. This patch made no difference what-so-ever on the timing results of the
>cygbench configure on my NTFS disks; then again, it may help FATxx/Samba/NFS
>people.

Only if there are a lot of symlinks, it seems.  Otherwise the code would never
be hit.  And indiscriminately setting it once for each thread could have some
negative ramifications when the program isn't manipulating any symlinks.

It's a good suggestion, nonetheless.

Corinna, this is your code, what do you think?  Maybe a per-thread
"initialized_yet?" global would be useful here.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2002-09-02 22:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02  8:20 A Simple Real World Benchmark for Cygwin Rick Richardson
2002-09-02  8:36 ` Ville Herva
2002-09-02  8:55 ` A Simple Real World Benchmark for cygwin Christopher Faylor
2002-09-02 14:34   ` Dan Vasaru
2002-09-02 15:02     ` Christopher Faylor [this message]
2002-09-03  1:28       ` Corinna Vinschen
2002-09-03  2:38         ` dvasaru
2002-09-03  4:52           ` Corinna Vinschen
2002-09-03  4:59             ` Robert Collins
2002-09-03  5:42               ` Corinna Vinschen
2002-09-03  9:05                 ` Dan Vasaru
2002-09-03 23:34                   ` Bjoern Kahl AG Resy
2002-09-04  1:55                     ` Corinna Vinschen
2002-09-04  2:10                       ` Bjoern Kahl AG Resy
2002-09-04  2:22                         ` Corinna Vinschen
2002-09-04 14:44                           ` BASH slow on network share scripts (was RE: A Simple Real World Benchmark for cygwin) Dan Vasaru
2002-09-04 20:07                             ` Christopher Faylor
2002-09-02  9:06 ` A Simple Real World Benchmark for Cygwin Michael Hoffman
2002-09-02 11:37   ` Randall R Schulz
2002-09-02 21:31   ` Jeremy Hetzler
2002-09-03 10:58 ` Eric M. Monsler
2002-09-04 10:54   ` Shankar Unni
2002-09-05 17:50 ` Randall R Schulz
2002-09-02  9:51 John Vincent
2002-09-02 10:36 ` Nicholas Wourms
2002-09-03  9:08 A Simple Real World Benchmark for cygwin Robb, Sam

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=20020902220234.GA22844@redhat.com \
    --to=cgf@redhat.com \
    --cc=cygwin@cygwin.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).