[opencms-dev] database problems with opencms

[Ron Wheeler]

You also need to be more careful about tuning as the database gets 
larger. Cache can make a big difference. Having appropriate indexes to 
support table joins becomes more important as the table sizes increase.

Joining large tables to each other can be problematic and may benefit 
from revised search strategies.
It may sometimes pay to select records of interest into intermediate 
tables rather than join 2 big tables and then extract the rows you need.

Ron

Dark Side wrote:
> Hi,
>> Hi,
>>
>> The amount of data which can be handled with OpenCms is a matter of the
>> database and not the application itself. Certainly it would be a 
>> problem if
>> you want to import 20 GB data with the data import wizard ;-), but 
>> there are
>> other ways to do it right.
>>   
> Of course its absolutely no problem to import 20GB with the OpenCms 
> database import/export tool, why should it? Made this more than one.
>
>> I know about OpenCms Installations with 30 GB data in it on Oracle and I
>> think with other dbs like MySQL it should be possible too.
>>   
> The same for MySql  -Database sizes >20GB work fine.
> The only thing I could think of where a "bigger" database could cause 
> a problem is if you run OpenCms and the database on the same machine 
> which is powerful enough - you should always have enough memory 
> available, this is more important than a faster processor.
>
>> Send my kindly regards to your professor ;-)
>>   
> Indeed, Volkmar should not believe everything his professor says.... :)
>
> Dark
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please 
> visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
>
>