Author Topic: Cache more blocks. (Read 960 times)

nend · « **on:** 10 Feb 10, 05:03:54 »

I know it is possible but will this be a part of the system in the future?

I don't see why html and script blocks are not cached already. Their output will never change unless edited.

PHP on the other hand changes but you have two options there. Cache the PHP code or cache the PHP output. If you cache the code you possibly eliminate a db request unless the code request one. If you cache the output you eliminate a db request all together.

Is this being looked into or at least considered?

Thanks in advance.

feline · « **Reply #1 on:** 10 Feb 10, 10:52:31 »

Quote from: nend on 10 Feb 10, 05:03:54

I don't see why html and script blocks are not cached already. Their output will never change unless edited.

what you want with a cache of html code?

Quote

Cache the PHP code or cache the PHP output. If you cache the code you possibly eliminate a db request unless the code request one. If you cache the output you eliminate a db request all together.

A output cache is't possible for the most blocks, because the content is user specific (isRead/notRead etc.) so we use a dbquery caching.

Fel

User

Community

Donate

Stats

Author Topic: Cache more blocks. (Read 960 times)

nend

Cache more blocks.

feline

Re: Cache more blocks.