#2502 - Tempcode optimisation - optimised caching

By Chris Graham
Added 25th Apr 2016, 5:43 PM
6 views

Identifier	#2502
Issue type	Feature request or suggestion
Title	Tempcode optimisation - optimised caching
Status	Completed
Tags	Type: Performance (custom)
Handling member	Chris Graham
Addon	core
Description	A powerful improvement would be an ability to do do_template calls in an 'optimise' mode. These calls would do a full template recompile each time, but as they know the exact parameters used then we could avoid storing the parameters within the Tempcode object separately, and have much simpler generated Tempcode. Things like IF directives on those parameters could be fully unrolled. Blocks with caching enabled would enable optimise mode while the blocks are first generating.
Steps to reproduce
Funded?	No

The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated

Comments

By Guest posted 25th Apr 2016, 11:33 PM

Small optimisation on top of this -- any boolean parameter can be pre-converted to '0' or '1'.

By Guest posted 19th Jun 2016, 12:53 PM

Further, for each symbol we can code whether than symbol can be flattened to a string if all its parameters are strings. This should be a very significant optimisation as a whole template instance may then become equivalent to a single string. If it is, we can set a flag in the object so when it gets attached to something else during optimise mode, it gets attached as string (i.e. evaluate gets called).

#2502 - Tempcode optimisation - optimised caching

Rating

Comments

Statistics