Any problems with SQL based CMS (joomla/drupal) and No. of connections

If you aren't on a dedicated server, will you have problems.

[cmendla]

I ran into a situation on a shared host where an oscommerce site wasn't working because the number of simultaneous SQL connections would exceed the available number. They had to switch to a semi dedicated host to get things working again.

I was wondering what happens when you run Joomla or Drupal and start getting a decent number of visitors. Has anyone had any experience with that?

The oscommerce was an older version so I'm wondering if joomla and drupal might be more efficient with the SQL.

My shared hosting offers 25 simultaneous sql connections I believe. I'm wondering where the break point is where you will start running out of connections.

thanks

cg.

[ergophobe]

It's going to depend a lot on your site. On drupal, for example, if it's a community site and most visitors are logged in, there's a lot of stuff you can't cache. If you have a lot of modules that require slow SQL queries and you're showing a "who's online" to everyone and so forth, that stuff will bring you to your knees.

If you have, on the other hand, a site that is primarily visited by anonymous users and only the admin logs in, you don't have a lot of heavy modules and up-to-the minute dynamic content, and you cache aggressively, you'll be able to approach the levels you would on a static site.

In other words, on a fairly static site, you'll still typically invoke PHP and create a DB connection, but you may have as few as one simple and fast request with some caching scenarios. In other scenarios, you may have dozens of requests for a single page and some of those requests will be joins on multiple tables and will be quite slow.