On 1/13/12, Petko Yotov <[email protected]> wrote: > On Friday 13 January 2012 04:37:02, Carlos AB wrote : >> * A mysql backend plugin would solve the problems concerning amount of >> content, user base and speed? > > It may solve the problem of "many editors saving pages at the same > millisecond" but to solve the other problems, special optimizations need to > be > made, one for listing and ordering huge numbers of pages -- use the database > engine for sorting instead of PmWiki --, and another one for indexing and > searching into these pages. BTW, to search among 2M pages, a dedicated > program > or server may be needed. > > There is also the DataQuery recipe. I haven't reviewed it, but it may be > usable or easier to adapt: > > http://www.pmwiki.org/wiki/Cookbook/DataQuery
The problem is bigger than what I thought, now I can see it more clearly, I would also have to change pagelist to take full advantage of a database engine. To not abandon the idea of using PmWiki for the project and be able to still use pagelist, can I restrict it in a way that it can only list pages in one group or a max of 5 or 10 groups, in each time it is used? With that I would not lose the functionality of pagelist and could work on other solutions for searching the whole site. > PmWiki is a tool for collaborative creation and maintenance of websites. It > is > more focused on the goal (websites) than on the process (community, editor > accountability). For the latter, I could suggest MediaWiki, or if you need > stuff like PageTextVariables, a Semantic wiki: > > https://en.wikipedia.org/wiki/Semantic_wiki I believe that the basic functions of pmwiki are ok for the site I want to build, and also the goals are in tandem with what I want . For the accountability of users, I prefer the "given enough eyeballs" technique, if reversing things to normal is easier or equal than creating problems for the wiki "all bugs are shallow". I want to have the site open just like the pmwiki site is, with lots of users, let's see what happens. :) Probably mayhem. I also wanted to have a functional instalation on the markup side and have pagelist working even with some limitations. so users can use it to create lists, search pages within a limited number of groups at least inside each artist space/group and be able to play with it. Other than that, the number of artists will result in more or less 50.000 groups, a per group wiki.d and a restricted pagelist to a max of 5 groups and maybe, just maybe, I won`t even need a mysql database plug-in, just a dedicated server and all types of caches enabled. What comes to mind is a folder with 2M cache files. Perhaps not using all 2M files from the start would be a good idea, also to have some participation and collaboration, otherwise the only thing left to do is to create problems. Thanks CarlosAB _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
