Edgewall Software

Ticket #1216 (new enhancement)

Opened 4 years ago

Last modified 2 years ago

wiki pages caching

Reported by: zilvinas Owned by: jonas
Priority: normal Milestone: 2.0
Component: wiki system Version: devel
Severity: normal Keywords: objectstore
Cc: zilvinas@…

Description

Most of the time wiki pages can be considered as a static content. So instead of generating and regenerating wiki pages -> html output, perhaps it would be useful to cache generated HTML output of wiki pages on the disk. Next time, page is requested checking if there have been changes - if not serve the file, otherwise - regenerate HTML page and serve newly generated file.

Sure this raises a question, what to do with embedded python macroses (see wiki-macros). Having such functionality, would help to reduce server load and would be very helpful especially with wiki rst (Restructured Text extension).

This ticket is rather an attempt to find out if there is a demand for such functionality. Consider this ticket as a discusion starting point.

Attachments

Change History

Changed 4 years ago by cmlenz

So... what about wiki macros? The content they generate could change anytime. Would only pages that don't contain wiki macros be cached?

Changed 4 years ago by anonymous

The way I think is the following:

Wiki pages caching is optional (either enabled or disabled by default). Assuming caching is enabled, during wiki page serving it is possible to detect if wiki page makes use of macroses. (Searching for [[ ]] should be enough). Perhaps initial version, for simplicity, should not cache wiki pages with macroses in them.

In future, caching system can be smart enough always to execute macroses only without need to reproccess whole wiki page ? (execute macros, insert it's output at appropriate place in preprocessed wiki page and serve it ... - perhaps that makes no sense).

Changed 3 years ago by cboos

  • keywords objectstore added

Also, note that idea of a cache could be expanded to other things as well, like changesets, fontified source files, ...

Disk is cheap, and a kind of LRU cache of a few Gbytes could speed things up quite a bit...

Changed 2 years ago by cboos

  • milestone set to 2.0

Add/Change #1216 (wiki pages caching)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change from jonas. Next status will be 'new'
The owner will change from jonas to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.