Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Anthony Martinez <pi+sup@pihost.us>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] index size
Date: Thu, 04 Mar 2010 10:32:31 -0700	[thread overview]
Message-ID: <1267723895-sup-8943@home.mrtheplague.net> (raw)
In-Reply-To: <b3095c51003040923r3cf7d6efl3fff5dbb4fdd6078@mail.gmail.com>

Excerpts from Juan Diego's message of Thu Mar 04 10:23:27 -0700 2010:
> So, could any of you guys please share with me the sizes of your index
> files and also the sizes of your mail sources (I guess the index size
> depends on the sources size so that I can make an estimate for my
> sources).

$ du -hs .sup/xapian Maildir
625M    .sup/xapian
765M    Maildir

> Thanks
> Have a nice day
> chao
No problem!

-- pi

-- 
All C programs do the same thing: look at a character and do nothing with it.
-- Peter Weinberger
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-03-04 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 17:23 Juan Diego
2010-03-04 17:32 ` Anthony Martinez [this message]
2010-03-04 18:48   ` Juan Diego
2010-03-04 17:42 ` Michael Stapelberg

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=1267723895-sup-8943@home.mrtheplague.net \
    --to=pi+sup@pihost.us \
    --cc=sup-talk@rubyforge.org \
    /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