Thread

Hi,

I run MSM and EE 1.6.7 and the DB is getting quite large. I was wondering whether there was a point when your DB gets so large (and your site is quite busy) that adding/removing custom fields becomes a hinderance? For example if the query starts lagging could it make the sites unavailable from the front end as the site is doing too much work on the Control Panel?

Thanks
Michael

It should not.  How many custom fields are you talking about and how large is your database?

I was wondering whether there was a point when your DB gets so large (and your site is quite busy) that adding/removing custom fields becomes a hinderance? For example if the query starts lagging could it make the sites unavailable from the front end as the site is doing too much work on the Control Panel?l

You’ll find that the answer is “server dependent.” I had a busy site with a 30-megabyte DB running on a shared server and during busy times login and updates were slow. Once I moved it to a faster server with faster DB, no problems at all. So, it’ll all depend on hardware, software configuration, and traffic.

How big is the DB? And what kind of hardware is being used?

not just hardware, but server and DB setup… I have seen hosts in the past restrict the number of concurrent connections, queries in a period of time, etc…
But yeah, bigger better faster would be good!

Well the DB in question is around 400MB and there are about 350 custom fields. Was EE designed to handle this amount of data?

Well the DB in question is around 400MB and there are about 350 custom fields. Was EE designed to handle this amount of data?

That’s a rather healthy size for a MySQL DB, but performance is dictated by other variables; traffic, site design, hardware (especially), configuration, etc.