i am interested in that too... if so. can help ;)
Magnolia - User mailing list wrote: > > We have had a medium sized site in Magnolia 3.0.x for about 6 months > now. There are about 40-50 pages in it I'd say, mostly all text. The > versioning is set to the default (which I believe is 2), and yet our > MySQL database is seemingly growing out of control. We keep the > authoring and public tables in separate databases and at the most recent > backup this morning, the authoring database is up over 950 MB, while the > public database is over 230 MB. The authoring one has grown over 50 MB > in the past 2 weeks, when I know that editing was pretty light due to > the holidays. > > Most of this space seems to be due to the version table. After dropping > the version tables the author database shrank to 55 MB and the public > one to 29 MB. Why are these tables growing so much if only 2 versions > of each page are being kept? It seems to me that 900 MB of versions is > quite excessive for that number of pages! > > Is there any way I can keep these repositories under control with the > versioning on, or is our only option to turn it off? > > Thanks, > Miranda > > -- > Miranda Jones > Objective Consulting, Inc. > http://www.spiders.com > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/docs/en/editor/stayupdated.html > ---------------------------------------------------------------- > > -- View this message in context: http://www.nabble.com/Why-is-my-database-so-large--tp14603434p14651965.html Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
