Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: manish@gslab.com (Manish Sapariya)
Subject: [sup-talk] Is sup slow on cygwin
Date: Sat, 26 Jan 2008 14:20:34 +0530	[thread overview]
Message-ID: <479AF45A.6060007@gslab.com> (raw)

Hi,
I am running sup on cygwin and using the mbox file
created by Thunderbird 2.0 on windows. I started
sup-sync and in almost 2 hours it just indexed 4
messages.

The folder that I am indexing has 270 messages and
size is around 17MB.

Is sup indexing expected to take this much time?

when I am running sup-sync or even sup, the CPU spins
100% all the time. In sup-sync output all I see is
output like..
===
## 3 (4.83%) read; 0:01:23 elapsed; 0:27:24 remaining
## 5 (4.84%) read; 0:02:31 elapsed; 0:49:35 remaining
===
What does first number denote?
And the remaining time goes very high if I keep running
when I kept it running for almost 2 hours, it said
remaining time is 61:12:43?

Any ideas?

Thanks and Regards,
Manish



             reply	other threads:[~2008-01-26  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26  8:50 Manish Sapariya [this message]
2008-01-26 19:42 ` Christopher Warrington
2008-01-27  4:14   ` Manish Sapariya
2008-02-03  4:24     ` William Morgan
2008-02-04  5:12       ` Manish Sapariya

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=479AF45A.6060007@gslab.com \
    --to=manish@gslab.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