Repost, as the original did not seem to reach the list.<br><br>Pm,<br><br>Can you please give a recommendation ?<br><br>Thank you in anticipation.<br><br>Christophe<br><br><div><span class="gmail_quote"><br></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I could not resist the temptation to experiment with PmWiki as data storage, as several recipes already do.<br><br>Compared to a database table structure,<br><br>- a PmWIki group represents a table<br>- a PmWiki page in this group represents a row of the table
<br>- PageTextVariable represent columns of the row<br><br>Using pagelists and pagelist templates, this approach works extremely well and offers many advantages, especialy considering there is no need for a database engine and the associated work.
<br><br>One drawback is of course the performance: a filtered/sorted/well presented pagelist with 2.500 pages/rows takes about 30 seconds to render on my host, which is much too long to be acceptable. The data I store do not currently change often (less than once a week).
<br><br>I understand there is work in progress on pagelist caching. Can we expect major speed improvement or is it not realistic ?<br><br>If not, or as a quick improvement before more important changes, could we somehow add an option to the pagelist markup like "StoreresultToPage=
groupname.pagename", that would save the result to a static page (which would not need to be recalculated each time) ? <br><br>If yes, this could be further improved by letting this process automagically happen once every n minutes, so that only one visitor every n minutes would have to wait for the full generation ?
<br><br>Any other ideas to improve speed ?<br><br>Thank you in anticipation.<br><span class="sg"><br>Christophe<br><br>
</span></blockquote></div><br>