Scalability in 2009

Events happening in the community are now at Drupal community events on www.drupal.org.
spiderman's picture

The BoF notes from DrupalCon DC here: http://groups.drupal.org/node/19737 mention that "When you have more than 100,000 contacts, it makes sense to look into other systems. Example: issues with Oregon Democratic Party site". I'm interested in knowing more about the question of scalability with CiviCRM.

What "issues" arose with the Oregon Democratic Party site? What version of Drupal/CiviCRM were they running? How many contacts did they have, exactly? What were the factors involved (ie. lots of custom fields, etc)? Are there other examples of sites with large numbers of contacts that worked well, or didn't? Are there ways of alleviating these kinds of problems right now? Are there plans to make CiviCRM capable of scaling better in future versions?

Comments

information is a bit limited ....

lobo's picture

we dont have a lot of info about the oregon democratic party site unfortunately. The consulting firm did not share any details with us or the community. that said it was on a fairly old version of civicrm (1.4 if i remember right). the newer versions of civicrm (2.2.x and 3.0.alphaX) have significantly improved schema and more tunable search parameters to improve scalability

if you'd like to discuss further please start a topic on civicrm forums

lobo

CiviCRM

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: