I am curious to what organizations consider a large member portal user base? Have you run into any issues scaling?

We estimate ~256MB per backend Civi user (for an intensive user). Since a member portal user will be prevented from interacting with Civi directly ( and no wp-admin access), what resource allocation should we estimate per member portal user?

We are using WP multisite and CiviCRM WordPress Member Sync. The portal is on the main site only.

  • Not an answer, but when looking at number of contacts, the stats site helps gauge where you are on the size spectrum stats.civicrm.org/?tab=sites
    – Aidan
    Feb 21 '20 at 9:04
  • This isn't really a question about CiviCRM resource usage, what you care about is resource usage of WP. You say above that portal users won't be interacting with CiviCRM, right? Resource usage is pretty difficult to estimate reliably - there are formulas that will give you an upper bound, but it's only in actual live production that you can tell how often your users will login. And there are tradeoffs - a faster processor will result in fewer concurrent requests, so you can get away with less memory, for example.
    – Alan Dixon
    Feb 21 '20 at 15:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.