From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] Sup is hangingyy
Date: Wed, 3 Jun 2009 21:53:12 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0906032152200.6894@javelin> (raw)
In-Reply-To: <1244078482-sup-4986@javelin>
On Wed, 3 Jun 2009, Edward Z. Yang wrote:
> The second is a large amount of CPU thrashing as Sup parses messages. This
> is something we can fix, and I hope to do some more poking to help make
> Sup run faster in this respect. The basic behavior is Sup repeatedly
> allocates some amount of memory, reallocates it twice (quadrupling it
> in size to about 4MB), deallocates, and then does it again. I'm running
> ruby-prof in hopes of tickling this again. Unlike the hung IMAP server,
> this eventually finishes, but it is extremely obnoxious when it happens
> and blocks everything else. It commonly occurs when I open an email message.
Here we go:
http://web.mit.edu/~ezyang/Public/sup-performance.png
Look at String::=~. Definitely not acceptable.
Cheers,
Edward
next prev parent reply other threads:[~2009-06-04 1:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 17:39 [sup-talk] Sup is hanging Edward Z. Yang
2009-06-03 18:11 ` William Morgan
2009-06-03 18:26 ` Edward Z. Yang
2009-06-03 18:21 ` Edward Z. Yang
2009-06-03 18:45 ` Edward Z. Yang
2009-06-03 21:36 ` William Morgan
2009-06-03 21:48 ` Edward Z. Yang
2009-06-04 2:11 ` William Morgan
2009-06-03 22:00 ` [sup-talk] Sup is hangingy Edward Z. Yang
2009-06-04 1:26 ` Edward Z. Yang
2009-06-04 1:53 ` Edward Z. Yang [this message]
2009-06-04 16:09 ` [sup-talk] Sup is hanging William Morgan
2009-06-05 5:08 ` Edward Z. Yang
2009-06-05 13:23 ` William Morgan
[not found] ` <1244227108-sup-3123@cabinet>
2009-06-05 21:47 ` Edward Z. Yang
2009-06-06 6:20 ` Edward Z. Yang
2009-06-08 18:09 ` William Morgan
2009-06-04 2:12 ` [sup-talk] Sup is hangingy William Morgan
2009-06-04 2:13 ` 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=alpine.DEB.2.00.0906032152200.6894@javelin \
--to=ezyang@mit.edu \
/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