[hydra-dev] Scalability

[Chris Tooley]

> I see your point, but I'd say that registrations or asynchronous
> messages then become something to count and that are not directly
> related to "subscriber" volumes.
>
> For instance: I am a call center.  I have 10,000 seats.  I have a re-
> REGISTER interval of 30 seconds.  Do I want to copy the exact system
> that an ITSP has who sells to 10,000 subscribers at retirement
> communities and has a re-REGISTER interval of 3600 seconds?
>
> These are things that we can't predict with any certainty, especially
> since we don't know what out-of-band requirements will be for future
> protocols.  So let's just base our number on the number of messages or
> volume of media packets...
>
> The more I think about it, the less meaningful a "size" number
> becomes, so I'm not sure that a subscriber count or message volume or
> any other such concept is really useful other than saying "a whole lot".
>
I agree with this sentiment exactly. It should fall more along the
lines of, "we don't impose much overhead and therefore don't greatly
impact the limitations imposed by the hardware selected to perform the
operation".