It's just the same as the Jackrabbit 1.3 jackrabbit-mysql-search.xml
file that comes with the 3.0.5 distribution, but with the
PooledJNDIDatabasePersistenceManager customization for the persistence
manager, like:
<PersistenceManager
class="com.iorga.jackrabbit.core.persistence.db.PooledJNDIDatabasePersistenceManager">
<param name="dataSourceLocation"
value="java:comp/env/jdbc/mysql/magnoliaAuthor"/>
<param name="schemaObjectPrefix" value="${wsp.name}_"/>
<param name="externalBLOBs" value="false"/>
</PersistenceManager>
Most pages are not edited much, if at all, after they are created. The
main exception is the home page, where there are about 6-7 small
"sections" (single paragraph block with a linked title), a couple of
which are edited weekly.
We have some custom paragraph dialogs, similar to ones found in the
samples distribution: section header text, section content text, a few
link related properties/booleans (link the header to another page, link
the text, external/internal link). The pages themselves just have title
and a javascript entry area for the most part. There's also some
aggregation and priority related settings, but they are not used on all
pages. The priority is used to set a meta tag for search indexing and
the aggregation properties are just a couple booleans and a text summary
that are used for a special template that we've written that creates a
summary page with links and summaries of all pages "below" it in the
site tree (so, for example, a /news.html page that has as summary list
of all the pages below /news).
Jan Haderka wrote:
Hi Miranda,
could you send your jackrabbit configuration file? (don't forget to
remove all sensitive information from it before sending the file).
Also could you try to describe what your typical piece of content and
workflow is? i.e. how many properties (title, description,...) does it
have and how many times do the users edit this single piece before it
gets published.
Thanks,
Jan
P.S.: I don't have an answer to your question yet, just looking at the
ways to replicate the situation.
On Mon, 2008-01-14 at 11:42 -0500, Miranda Jones wrote:
Sorry for the "bump" but I'm hoping that maybe someone will be able to
shed some light on this. We would really like to keep giving our client
the option to revert to previous versions if they need to but the
database size is getting out of control. In the 11 days since my
original message, our author database has grown another 30 MB and the
public one has grown another 10 MB without any significant editing (all
new pages or edits are text only).
Thanks,
Miranda
Miranda Jones 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
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
--
Miranda Jones
Objective Consulting, Inc.
http://www.spiders.com
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
