On 3/22/2018 7:38 AM, Foster Schucker wrote:
I ran an internal wiki at a company that had just over 22K pages. No problems with memory or performance.

I also think that 1 billion pages in a wiki is a push. I can see building "Face Wiki" in light of the recent FB issues, but there is a little more involved at that level. You are going to want a distributed wiki front end to be able to handle the load.

Mediawiki has worked on the multiple wiki front ends to one/few backing stores. You might want to look at that.

Good luck!

On 3/22/2018 5:20 AM, Jim Willeke wrote:
http://ldapwiki.com/   has 13,278 pages.

--
-jim
Jim Willeke

On Thu, Mar 22, 2018 at 5:10 AM,lgilardon...@gmail.com  <
lgilardon...@gmail.com>  wrote:

That's a good point Jürgen.

This however raised two question in my mind.
First one is that *could* be a main point for future work (it would mean
to build a persistent intralinks repo to be buid and maintained
incrementally on pages change - which is surely a major overhaul but does
not look like rocket science).
Second one however - as a consequence - is .. when this would became a
real issue? 1k pages (believe not - we are running an intranet
that order of magnitude size and does not looks a real issue)? 10k? 100k?
Last consequential answer .. letting apart rebuilding wikipedia (which it
is not a real case i guess - and anyway as from
https://en.wikipedia.org/wiki/Wikipedia:Size_comparisons
it is far from that number) I hardly can image a 1B pages wiki.
@dagarwal82 may we know which kind of wiki (i.e. which kind of content)
are you thinking about?


On 3/22/2018 8:26 AM, Jürgen Weber wrote:

guess not, on startup JSPWiki loads all pages into memory to parse
intra-page links.

2018-03-22 5:24 GMT+01:00dagarwa...@gmail.com  <dagarwa...@gmail.com>:

JspWiki uses filesystem instead of a conventional database. Would you
suggest using jspwiki if it were to cater to 1billion page ? (Provided, a
solid backup mechanism ). Would it scale that much with both performance
and data-integrity perspective ?

Reply via email to