3 ms·
We're getting into the weeds here, so don't feel the need to reply. I agree there's different complexities, and both ways will be complex in some places, and si
by toast0 7y ago
We're getting into the weeds here, so don't feel the need to reply. I agree there's different complexities, and both ways will be complex in some places, and simple in others. I just want to address this one thing.
> you would have hundreds of millions or even billions of actors being idle all day long
> but at least no massive overhead from idle workers.
You could certainly work to activate the actor for a user only when it's needed (while the user is online, or while an email is delivered); but the level of overhead for an actor is quite low --- it would be fine to have the actor simply always running, and doing nothing when there's nothing to do. You can run a million Erlang processes on a server, and if they're mostly idle, there's no big deal; if you need to run a billion processes, you would need a thousand servers; but my wild guess is storage is going to be a bigger factor than CPU, assuming that the gmail style large quotas do get significantly used, I could easily be wrong about storage requirements though.
- tsimionescu 7y agoAgreed, we're getting in too many vague details. I didn't know that Erlang can go up to such large numbers of processes, I knew they were very lightweight, but would have guessed maybe at most thousands to tens of thousands. Very nice that they can do that!