Reaching out about Jackrabbit performance and scalability...
Robert Botzer <Robert.Botzer <at> axispointhealth.com>
2016-04-28 15:55:24 GMT
I am looking for any thoughts and info about how much volume a single instance of a Jackrabbit server can handle...
Especially if anyone has experience with using it as a component of a large web based
(and if there is a way and how to measure / predict that..)
Here is some background on what I'm looking for...
We are currently using a Jackrabbit server and content repository as a component of our web application
solution. ( I believe it is 2.2.13 )
We are storing simple text documents like 1 page notes, or 1- 5 page letters.
We are using simple file system storage, and we store a reference link to the document in our relational database.
We DO NOT do any searching against these documents. (So we have turned that indexing off..)
So basically we upload a small document, keep and store the reference to it, and retrieve the doc based on that.
We also use a hashing algorithm to distribute documents to separate folders so we do not run into file system
(like 20,000 files in one directory).
We can scale our web application server 'out' by having multiple instances behind a load balancer...
But all of those instances currently use the same (singular) Jackrabbit server / repository.
( btw: The file system repository is on the same server as the Tomcat/Jackrabbit instance - so no network
access for Jackrabbit to access the docs.)
We are having good results with 3 of our application servers - for ~ 600 users, using a single Jackrabbit instance...
However, we have a new prospect/client that is asking for ~ 3000 users... So we could be deploying something
like 30+ servers each connecting to Jackrabbit
I think that ultimately the actual Jackrabbit load will likely depend on how many documents per minute ( or
some unit of time).