From: Gregor Hoffleit <gregor@hoffleit.de>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup-server revisited
Date: Thu, 03 Mar 2011 18:32:34 +0100 [thread overview]
Message-ID: <1299172989-sup-8183@sam.mediasupervision.de> (raw)
In-Reply-To: <1299091467-sup-7084@masanjin.net>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
William, I was able to isolate my problem: For me, heliotrope-add hangs
for messages with more than 32768 content lines.
I have attached two mbox files, each containing a single message.
The message in good.mbox has 32768 content lines (excluding header) and
has no problem in heliotrope-add. The message in bad.mbox has 32769
content lines, and heliotrope-add hangs when trying to add this message.
I haven't yet tried to locate the locate the problem in the source.
Regards,
Gregor
* William Morgan <wmorgan-sup@masanjin.net> [Mi Mär 02 19:51:58 +0100 2011]
> Reformatted excerpts from Gregor Hoffleit's message of 2011-03-02:
> > I can't give away the mbox file. Any hints how I could debug the
> > heliotrope-server script?
>
> Can you isolate the message? It might be that it has a huge attachment
> that RMail is taking forever to parse, and that results in a client
> timeout.
>
> I need to move the message processing out of the request loop,
> obviously.
>
> As a workaround (which also is much faster), kill the server, wipe
> everything, and use `heliotrope-add -d <dir>` to import an mbox or
> maildir without having to go through HTTP.
>
> > Nice work otherwise! The web client is a nice demonstration of what
> > might come out of this project ;-)
>
> Thanks! I'm currently working on stripping everything out of Sup that
> will be handled by the server. The good news is that this is a LOT, and
> that Sup will be much leaner and meaner than before.
[-- Attachment #2: mbox-32768lines.tar.gz --]
[-- Type: application/x-gzip, Size: 804 bytes --]
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-03-03 17:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 21:02 William Morgan
2011-02-22 13:46 ` Mark Alexander
2011-02-22 17:55 ` William Morgan
2011-02-22 18:44 ` Tero Tilus
2011-02-22 19:00 ` William Morgan
2011-02-22 14:09 ` Nicolas Pouillard
2011-02-22 20:17 ` Tero Tilus
2011-02-22 21:29 ` William Morgan
2011-02-23 9:48 ` Nicolas Pouillard
2011-02-23 18:43 ` William Morgan
2011-02-23 18:53 ` Alvaro Herrera
2011-02-23 21:08 ` William Morgan
2011-02-23 21:30 ` Alvaro Herrera
2011-03-03 19:38 ` Sascha Silbe
2011-02-26 19:15 ` Hamish
2011-02-26 22:04 ` William Morgan
2011-02-26 23:15 ` William Morgan
2011-03-01 19:38 ` Hamish
2011-03-02 12:43 ` Gregor Hoffleit
2011-03-02 18:51 ` William Morgan
2011-03-03 17:32 ` Gregor Hoffleit [this message]
2011-03-03 19:17 ` William Morgan
2011-04-15 10:46 ` Gregor Hoffleit
2011-04-15 17:16 ` William Morgan
2011-04-15 20:53 ` Gregor Hoffleit
2011-04-17 16:58 ` William Morgan
2011-04-17 17:55 ` 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=1299172989-sup-8183@sam.mediasupervision.de \
--to=gregor@hoffleit.de \
--cc=sup-devel@rubyforge.org \
--cc=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