andi
140k pages is a lot for sure. Are you sure your departments will produce that many pages? Manually? I would assume that it would take them several years to reach this amount (unless you have some automatism to convert a lot of existing documents to wiki pages).
Anyway, 140k pages might make the search a bit slow. One of the available search plugins could solve this. You will not run into this problem when using farming.
However the question you should ask yourself is how much interaction between departments do you expect/want. If departments regularly look for information provided by other departments, farming would get in the way. However if your departments should be fairly autonomous, farming would be a good solution as it would also allow you to appoint admins per department.
andi
One more thing: you could also start with a single wiki and split it up into a farm later on. Or vice versa. It's not like this decision has to be forever.
vicentmas
I'd like to install a wiki engine in my organization. Its departments should use the wiki for creating and managing internal (non visible from the Internet) documentation (normally non technical documentation as the organization belongs to the local government and most of work here is administrative). There are about 70 departments with an average of 10 members. I expect that every department would manage about 2000 pages.
I'd like to know if DokuWiki fits well in this scenario or on the contrary it cannot scale well to that number of documents.
My second question is: if the wiki described about is too large for DokuWiki, would it help to create a farm of wikis? In other words, would it help to have a farm with about 70 animals (and about 2000 pages per animal) instead of a large single wiki?
TIA
vicentmas
I forgot to mention/clarify a couple of details:
- as the documentation will not be available from the Internet (as I mentioned the wiki is for internal use) the number of visitors would be small
- the number of regular authors per department would probably be small too, no more than three regular contributors are expected
Please, tell me if you need more details in order to answer my questions.
Thanks again.
vicentmas
Hi!
140k pages is my most pessimistic estimation, but it could happen in the future. Information in the wiki should be private to every department (information of global interest has its own place) so accordingly to your answer farming fits well in my case and solves the problem of slow searching too. That's just great. I'll definitely try dokuwiki.
Thanks a lot for your help!
PS: thanks also for your last advice about moving between farm and single wiki if required.
xelarix
Hello Andi,
that, what you are mentioning, is exactly what we're looking for. But we didn't find a proper documentation.
Our department has a DokuWiki grown over time (>10 years). Now our department experiences a "reorganization", so teams get split up. etc... This of course also affects our DokuWiki instance. As a first step we sorted everything in namespaces. But for some parts/namespaces it becomes more and more reasonable to split things up using farms.
So our question here basically is: "how to do it?". How to divide things up (pages, media files) and keep revisions etc. consistent at the same time? Is it just copying files into the respective 'animals'?
Thanks in advance for your answer.
Kind regards, XelariX.