Jeff, This is likely because of all the tables that the Field SQL storage module creates (2 tables for every field). You may be interested in checking into the Per-Bundle Storage module (http://drupal.org/project/pbs).
Dave Reid [email protected] On Mon, Dec 6, 2010 at 2:08 PM, <[email protected]> wrote: > Don't get me wrong, I'm chuffed to mint balls about the D7 effort and the > result, for many reasons, not least of which is the amazing talent > represented by it. > > > That said, I received a letter today from the hoster stating that my > account was a performance problem because it had over 1000 tables. Eight > Drupal sites coud be over 1000 tables. > > > I have a hosting account with 'unlimited domains' and up to 25 databases. I > use the account both for hosting several live domains, most multi site, as > well as a test area that clients can access for testing changes to existing > domains. 8 Drupal sites could be over 1000 tables with the typical array of > add-on modules, let alone that most of these sites are doing e-commerce. > > > I've let them know that they might want to consider a more meaningful > indicator of performance issues than a script that counts tables, since > probably none of these sites does more than 100 transactions per day. If > they hold firm, I'll blog (and post here) their name. > > > Jeff > -- > > Ayen Designs > 388 Bullsboro Drive #105 ยท Newnan, Georgia 30263 > 404-271-9734 > Web:ayendesigns.com > Blog: theAccidentalCoder.com <http://theaccidentalcoder.com> > Drupal: j. ayen green <http://drupal.org/user/367108> > IRQ: j_ayen_green > IM (Yahoo) baalwww (MSN) [email protected] > Skype: ayendesigns > > Ayen Designs is a tradename of the computer services division of >
<<ayenlogo>>
<<acmelogo>>
