CiviCRM Community Forums (archive)

Hi everyone,

I love CiviCRM - kudos to the creators and maintainers. Truly awesome stuff.

I have 3.0 installed on our Drupal 6 site, with its own database. I wanted to move our event system over to CiviCRM, for registration as well as for our calendar view (and the Upcoming Events block). The problem is, when I add the db_prefixes to settings.php so the events can show up in a calendar view, the site becomes way slower. I know I've just doubled the number of database tables that might need to be referenced in queries, but the slowdown is much too much to be acceptable for end-users. But is this really the normal behavior?

Thanks,
Jugney

No takers? I'd be happy to provide more information if needed.

I have other modules installed, but the effect is so pronounced that it's clear the cause is the additional db tables being exposed in settings.php.

Anyone?