Apache Jackrabbit Scalability and Performance

["Shah.Abhishek" <en...@gmail.com>]

Hi,

We are implementing a CMS for storing account related documents. Our
approximate requirement of storage would be around 1 million documents(350kb
each) per annum, which comes around 340GB of data approximately. 

I would like to know if Apache Jackrabbit can be scaled to that extent
without compromising on performance or consistency. 

Thanking in advance



--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Apache-Jackrabbit-Scalability-and-Performance-tp4660147.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Re: Apache Jackrabbit Scalability and Performance

["Shah.Abhishek" <en...@gmail.com>]

Forgot to add, we don't have a deep hierarchy. Hence number of child nodes
per parent node will be high. And we can't opt for clustering.



--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Apache-Jackrabbit-Scalability-and-Performance-tp4660147p4660148.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Re: Apache Jackrabbit Scalability and Performance

["Shah.Abhishek" <en...@gmail.com>]

Hello,

To all those who visit this post with similar queries, we did performance
testing for the above scenario.
with a hierarchy upto a depth of 3 level, we were able to store 2million
documents.
Size exceeded 500gb and the performance was pretty much under the expected
industry standard. (Can't disclose the figures as I ain't allowed)
Server used was a commodity server.
There was a lag and inconsistency observed when concurrent users tried to
upload under a same node at same time, but that can be handled by decent
login module.

Hope this helps



--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Apache-Jackrabbit-Scalability-and-Performance-tp4660147p4660524.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.