From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Using DTrace to profile sup-sync
Date: Sat, 15 Dec 2007 11:25:45 -0800 [thread overview]
Message-ID: <1197745662-sup-1441@south> (raw)
In-Reply-To: <ddd65cda0712150705j6543cbd9ud13d479708171223@mail.gmail.com>
Excerpts from Jjgod Jiang's message of Sat Dec 15 07:05:04 -0800 2007:
> When I was trying to build index for my GMail account (which has 28525
> mails in inbox) with sup-sync, I found the estimated finish time is
> too long (24 hours) to accept. So I decided to use DTrace to do some
> profiling work on sup-sync, and here is the result.
Thanks for the analysis! I am very interested in speeding up this sort
of thing. However, it looks like the culprit here is the Ruby IMAP
library, which presumably is so much slower than Mutt because it's Ruby.
So probably the only significant way to speed this up would be to use a
different IMAP library. If there's a C IMAP library with a Ruby bridge,
I'll consider hooking it in, but I don't know of one...
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-12-15 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 15:05 Jjgod Jiang
2007-12-15 19:25 ` William Morgan [this message]
2007-12-15 19:38 ` William Morgan
2007-12-15 21:04 ` William Morgan
2007-12-19 4:38 ` William Morgan
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=1197745662-sup-1441@south \
--to=wmorgan-sup@masanjin.net \
/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