Foren / Cotonti / Core Labs / Archive / Actual Caching - Proper Static pages

Lombi
#1 13. Januar 2009, 22:01
undefined:
Static Pages
If all the other caching methods are not enough or you can’t apply them, there is a last solution: Caching the complete generated pages. This can be done via an excellent plugin called WP-Cache. The plugin will cache the whole generated page on the disk and skip the complete WordPress execution on further requests. After a specified time or if you publish a new post, the cache will be cleared and generated once again. This method is the fastest available, but it will break some functionality like plugins which add dynamic content to your blog or count page impressions since they are executed only once. Note: If you want to use this plugin and the PHP Compiler Cache APC together, have a look at this posting from Mark Jaquith.

We created a system like this, actually exactly like this. It parses the whole page element and saves it into a supercache table.

It could be expanded to the forums and then deleted on reply/comment/review/edit

You wouldnt believe how much load this saves.

Should it be one of the core things that cotonti offers?
<a href="http://www.domenlo.com">Surreal Art</a>
Trustmaster
#2 14. Januar 2009, 00:38
Yes, it would be a stronghold for overloaded sites to have such an option. Is it a plugin or a corehack?
May the Source be with you!
Kilandor
#3 14. Januar 2009, 02:19
With the positioning of current hooks, only corehacks could be done, without some changing.

There are issues with this that would only make it pluign acceptable.

Dynamic things become static, can create HUGE database (not possible for everyone).
So it majorly decreases load, but has some sacrifices.

Hooks will be getting some rework anyways i think later. So adding a hook at the start of the file, will allow for something such as this to be easily created for those that choose.

Most users will never have a need for such systems. But we all know Lombi isn't Most users :)
Trustmaster
#4 14. Januar 2009, 02:57
That's why I say it should be optional. But it is a big deal for huge sites.
May the Source be with you!
musiconly
#5 14. Januar 2009, 17:22
# Kilandor : But we all know Lombi isn't Most users :)

Lombi is everywhere :-D

I'd like to see this in action, since I got pwned from most hosts just because of the caching system.. heck, i talked with my host provider an hour ago, they'll send me something related to sed caching system - looking forward to see what it's gonna be..
m_ogz
#6 2. Februar 2009, 04:12
# Kilandor : With the positioning of current hooks, only corehacks could be done, without some changing.

There are issues with this that would only make it pluign acceptable.

Dynamic things become static, can create HUGE database (not possible for everyone).
So it majorly decreases load, but has some sacrifices.

Hooks will be getting some rework anyways i think later. So adding a hook at the start of the file, will allow for something such as this to be easily created for those that choose.

Most users will never have a need for such systems. But we all know Lombi isn't Most users :)

I don't understand how it can create huge database. As I understand (maybe want), caching will be showed only visitors, not registered users. If someone adds a message on forums or other pages, the cache could reload. Also no one have to use caching system. On config.php, there can be an option for cache = TRUE or FALSE. And YES it must be one of the core things that cotonti offers...
Ne hasta bekler sabahı, ne taze ölüyü mezar, ne de şeytan bir günahı, seni beklediğim kadar;<br /><br />
Geçti istemem gelmeni, yoklugunda buldum seni, bırak vehmimde gölgeni, gelme artık neye yarar...
Lombi
#7 2. Februar 2009, 04:48
Anctually the way supercache has been designed, mainly because of my overabusive server crazy experimentation is that it is a "true cache", not like the "seditio cache" was supposed to do now, but a true cache. Since the seditio cache doesnt really cache much.

This cache is a system for portals with a major number of pages. I'm talking about 300.000+ more (it was developed for a 350K and a 500K DB). What I'm also taliking about is content that isnt changing. So it's not updating, at least not how it's designed now...
<a href="http://www.domenlo.com">Surreal Art</a>
m_ogz
#8 2. Februar 2009, 05:12
Ok. Isn't it possible to reload cache not only with time but for example with a function on forums.editpost. If I'm way behind the stuff, I won't speak again about caching :-)
Ne hasta bekler sabahı, ne taze ölüyü mezar, ne de şeytan bir günahı, seni beklediğim kadar;<br /><br />
Geçti istemem gelmeni, yoklugunda buldum seni, bırak vehmimde gölgeni, gelme artık neye yarar...
Lombi
#9 2. Februar 2009, 05:28
Of course it is. And it's simple as heck to do. But right now it was designed for my own needs and no pages get changed on those sites.

We;re still waiting for people to get interested in this plugin so we can release it.
<a href="http://www.domenlo.com">Surreal Art</a>
musiconly
#10 4. Februar 2009, 05:26
God dammit!!

E-Mail from my hosting provider, just an hour ago.. Long story short : "your cms caching system is retarded. it's eating our mysql. fix this soon, or we're gonna have a major problems.. we recommend you "php cache lite".. mail us if you have problems with implementation, maybe we can help you out!"

now, this bolded text is bolded only for one reason : my hosts never offered me any help. they just asked me to move on another server.. so this is a big plus for my current host! :)

ok, back to the problem.. what the hell I can do? i'm using seditio v125 and i'm afraid of moving to cotonti (yet).. thing that scares me most is part about "mysql encoding".. man, if lombi didn't manage to get it workin right, how the hell i'm gonna do that :D

i need a fast solution, what can i do to improve situation in 2 days or so?

desperately needing your help :(
Trustmaster
#11 4. Februar 2009, 05:54
Disable Seditio's cache. You can also convert the sed_cache to InnoDB.
May the Source be with you!
musiconly
#12 4. Februar 2009, 23:33
thanks trust and also big thanks to lombi :)

i've disabled cache, truncated the _cache table and changed to InnoDB..

now waiting for my host to reply if this helped!