From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Will sup blow up after adding 10k sources?
Date: Tue, 29 Jun 2010 09:15:56 -0400 [thread overview]
Message-ID: <1277817081-sup-1172@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1277801600-sup-3476@twin.sascha.silbe.org>
Excerpts from Sascha Silbe's message of Tue Jun 29 04:54:22 -0400 2010:
Hi Sascha,
> Wouldn't it be better to (*) use small fixed source ids for
> SentManager/DraftManager and let SourceManager start above a number
> of reserved ids (say: 50)? Is there something in sup that depends on
> the non-special source ids not to have "holes" (or will waste
> resources in that case)?
I agree that this would have been a better choice early on. Assign
the lowest possible id's to the Sent/Draft sources and then hand out
id's dynmaically from there.
> Another approach would be to make the SentManager/DraftManager
> source ids dynamic and add them to sources.yaml.
I'd have to look, but changing these id's after they've been used will
cause problems requiring a resync, I believe.
I'm sure others that have been more active in this part of the source
lately can provide more info too.
HTH.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-06-29 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 8:54 Sascha Silbe
2010-06-29 13:15 ` Ben Walton [this message]
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=1277817081-sup-1172@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=sup-devel@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