public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: locate and updatedb
Date: Thu, 11 Feb 2016 22:39:00 -0000	[thread overview]
Message-ID: <56BD0D87.6030008@gmail.com> (raw)
In-Reply-To: <56BCD414.2010304@zoho.com>

On 11/02/2016 19:33, Byron Boulton wrote:
> On 2/11/2016 1:18 PM, cyg Simple wrote:
>> On 2/11/2016 9:00 AM, Byron Boulton wrote:
>>> Does anyone here have success using `updatedb` and `locate` in cygwin? I
>>> use `locate` heavily on my Linux machines, but everytime I've tried to
>>> run `updatedb` on cygwin I've given up and killed the process because it
>>> is taking too long. Is there something wrong with cygwin's
>>> implementation of `updatedb` making it not work at all or making it
>>> slower that on my Linux machines? Or are there others who have success
>>> using it on cygwin?
>>
>> Processing every file on the drive will be slow just because it's
>> Windows.  Initializing the database with updatedb will require a large
>> amount of time.  There are processes such as AntiVirus intrusion
>> protection that might make it even slower.
>>
> Hmmm, the reason the slowness is particuarly strange to me is that in
> place of using `locate` from my cygwin terminal, I have to use a program
> called "Everything Search Engine" available at www.voidtools.com. The
> first time I install it, it takes maybe a few minutes to index the hard
> drive, then every once in a while when I open the program it takes a few
> seconds to update the index, but in general the performance for indexing
> and searching the index if comparable to `updatedb` and `locate` on a
> Linux machine, so it's possible to do on Windows.
>
> Byron
>

the time taken from updatedb is mainly due to
the execution time of "find" on the disks.

It takes ~ 70 minutes for my 500 GB of data,
and likely the AV is impacting the execution.

I suspect voidtools is using MS disk indexing
to speed up the things for it.


Regards
Marco




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-02-11 22:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 14:01 Byron Boulton
2016-02-11 18:17 ` cyg Simple
2016-02-11 18:34   ` Byron Boulton
2016-02-11 22:39     ` Marco Atzeri [this message]
2016-02-13 12:15       ` Linda Walsh
2016-02-16 22:55         ` Buchbinder, Barry (NIH/NIAID) [E]
2016-02-17 13:43           ` Byron Boulton
2016-02-17 16:01             ` Buchbinder, Barry (NIH/NIAID) [E]
2016-02-17 16:21               ` Byron Boulton
2016-02-17 16:49                 ` Buchbinder, Barry (NIH/NIAID) [E]

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=56BD0D87.6030008@gmail.com \
    --to=marco.atzeri@gmail.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).