[TYPO3-performance] Cache priming

[Stephan Schuler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Jonas.

You're free to improve every single edge of TYPO3 caching and contribute whatever you think is required.
But until now there is only backend API clearing mechanisms.

As stated by both, Philipp and me, creating content and determining corresponding cache metadata (identifiers, tags, privileges) is such a complex task which makes it nearly impossible to have a common behavior which fits for every case.

And ontop of that, FE rendering is such a complex task itself that reproducing behavior in BE is nearly impossible. So you would need to hit every FE page through some crawler anyway.
Search TER for "crawler" extension. There already is such a thing. It doesn't cover different FE groups, but for a simple "regular user" situation that should be enough.

Regards,



Stephan Schuler
Web-Entwickler | netlogix Media

Telefon: +49 (911) 539909 - 0
E-Mail: Stephan.Schuler at netlogix.de
Web: media.netlogix.de




netlogix GmbH & Co. KG
IT-Services | IT-Training | Media
Neuwieder Straße 10 | 90411 Nürnberg
Telefon: +49 (911) 539909 - 0 | Fax: +49 (911) 539909 - 99
E-Mail: info at netlogix.de | Web: http://www.netlogix.de

netlogix GmbH & Co. KG ist eingetragen am Amtsgericht Nürnberg (HRA 13338)
Persönlich haftende Gesellschafterin: netlogix Verwaltungs GmbH (HRB 20634)
Umsatzsteuer-Identifikationsnummer: DE 233472254
Geschäftsführer: Stefan Buchta, Matthias Schmidt



- -----Ursprüngliche Nachricht-----
Von: typo3-performance-bounces at lists.typo3.org [mailto:typo3-performance-bounces at lists.typo3.org] Im Auftrag von Jonas Eberle
Gesendet: Montag, 26. Januar 2015 14:31
An: typo3-performance at lists.typo3.org
Betreff: Re: [TYPO3-performance] Cache priming

Hi Philipp,

Am 22.01.2015 um 13:16 schrieb Philipp Gampe:
> You will never hit a page cache if you just cleared it. If you hit the
> page cache, then everything is fine. Therefore you should take proper
> care to *invalidate* caches correctly, e.g. clearing all effected
> caches. TYPO3 CMS 6.2 has lots of options for this. Best regards

I see. I could use e.g. https://github.com/TYPO3-coreapi/ext-coreapi 's PageCache-function to clear a specific page cache and then right afterwards fill it by fetching the URL.

Or I could use the other page clearing mechanisms (hooks, TSConfig, manual calls from my extension, ...) to clear the page. But then I still miss a regeneration of the page cache. If I do not do anything else, it will be the first user looking at the specific page that regenerates the page cache.

I am still not convinced that what Typo3 offers is ENOUGH to make performant sites.

Regards,
Jonas


- --
Neu: welcome.region-stuttgart.de
Neu: ladenbackofen.de
Neu: beltamor.de
- --------------------------------
d-mind bei Facebook:
http://www.facebook.com/werbeagentur.internetagentur.stuttgart
- --------------------------------
d-mind
Fuchs/Weiß/Strobel GbR
Mörikestraße 69
70199 Stuttgart

Tel.: +49 711 280481-1 (Durchwahl: -18)
Fax:  +49 711 280481-3
Inhaber: Jens Fuchs, Michael Weiß, Jens Strobel www.d-mind.de

_______________________________________________
TYPO3-performance mailing list
TYPO3-performance at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-performance

-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 3.3.2 (Build 15704)
Charset: utf-8

wpUDBQFUxlc9pp0IwsibV8MBCMcbBAC9XzDp6ijowrX0tyKnaGF2VVOHRQVPj9GG
lntrfdSjw/7Y5DxrWX0rEr2smc0JD0nYzEOjW1l6sLuf7ygwuxjVSC8x2y94bC8p
hVPD82R5lBtPoGBKqOKxBXDPAumiSRxUK9xXSuetj/gCSu6s/Dvd4T1CuJNx8sLq
Mh/9T6QTNA==
=oaY0
-----END PGP SIGNATURE-----