Concurrent sessions vs concurrent logged in users

I have an app that peaks at 3000+ concurrent sessions, and account creation is currently disabled.
Will enabling “Meteor accounts” cause too much overhead, or should I just create a non-reactive custom account system?



Now that’s an interesting question.

On the client, Meteor Accounts obeys the Tracker convention for transparent reactive programming. Values such as Meteor.user() (the database record of the currently logged in user) and Meteor.loggingIn() (flag indicating whether a login is in progress and a progress indicator should be shown) work as reactive variables.

With that said, only process affecting tracker event could be treated as “reactive”.
Though you are able to disable tracker hooks, nullifying accounts reactivity.

BTW, user accounts is not resource-heavy, so you should try an easiest approach first.