Ricardo Kustner wrote: > Hi, > > Gerard van Enk wrote: > >>> article. Could it be that this has a negative effect on the >>> performance of mmbase? I've noticed this mmbase installation is >>> extremely slow for an X amount of time after startup... >>> Since all these records are related to something, the install_insrel >>> table is quite huge too... >> >> If you don't have indexes on these tables things can be very slow. > > > Ah I see, I'll check if everything is properly indexed. > >>> A related question I have on this: if an object has an expire time >>> set, will it be deleted from the database if it expires or will it >>> simply not be displayed (in other words: do objects stick around for >>> ever in the database?) >> >> Expire time isn't an MMBase-thing, at least the basis install doesn't >> have this, so it must have something to do with your application. >> Maybe the webpages don't show objects after their expire time? > > > Oh I thought it was a standard property of all objects... I was just > wondering about this because the number of objects grow by time and with > certain builders like this one, the amount grows *very* fast... so in a > few years time you'll get a huge amount of objects... it's nice to keep > an archive of all old objects but the question is how long can it keep > growing before you run into trouble? :)
I don't think you'll run into trouble very soon (the vpro and eo both are having an MMBase-Cloud with a couple of million objects in it). Gerard
