[TYPO3-performance] SEO-Urls and Performance

[Stephan Schuler]

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

Hey there.

You should really tell some numbers to clarify what's a high load page for you.
I can't tell you any of mine because I don't know them. But whoever is willing to compare his performance with yours might need those numbers.
What's the 25ms for? For one page load? For 1000 typolinks generated?

We use realurl exclusively. We tried other mapping mechanisms every now and then but usually at some point there are some missing features that realurl just provides. I can't tell you any specifics because it's been quite some time now since we last checked, but I know that's usually the reason to stick to realurl.

Did you find out if it's realurl or the typolink itself? Did you get real performance improvements when disabling realurl completely just to find out if it *can* get any better at all?

I tend to introduce lots of caching wherever possible.
When rendering list views a single list element can be easily cached as a section.
If it's database backed list views, the list view itself can be completely cached, too, because you just know when the list content changes -- whenever somebody adjusts the database. Cache clearing based on data handler is done automatically.
Combine those: Each list element can be cached based on the actual item rendered, the list as a whole can be cached based on the table. This results in cache clearing not to clear *everything* but only a small fraction.
If it's e.g. solr backed where you simply don't know when your results change, then you might need to stick to section wise caching. But that *could* be enough.

If it's really a heavy load page, there might be no reason to clear caches *every tick*. Think about e.g. some kind of contest game where fe_users vote for something. You don't need to clear a single objects cache whenever a new vote goes in if that happens multiple times per second. Set up e.g. varnish and tell it to cache at least 2 or 5 seconds.

You see, I never thought about moving away from realurl because of performance reasons. If it's realurl to slow my page down I tend to rethink if that amount of link creations are really wanted and usefull.

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, 15. Dezember 2014 10:58
An: typo3-performance at lists.typo3.org
Betreff: Re: [TYPO3-performance] SEO-Urls and Performance

Dear list,

Sorry, I need to catch up on this.
Asked differently: do you use realurl in high-load environments?

Best regards,
Jonas


Am 11.12.2014 um 10:13 schrieb Jonas Eberle:
> Dear all,
>
> tl;dr: realurl is slow. we are looking for a lightweight solution to
> generate <a href>-links for freely assignable SEO-Urls and a solution
> to send incoming requests to the corresponding pages/plugins/actions.
>
>
> for a new project we are considering the performance of SEO-Urls.
> These are the requirements:
> * high-load site
> * many lists (or maps) with many objects that need links to their
> detail pages
> * strong focus on SEO
> * the links need to be COMPLETELY user-definable (probably down to any
> single object) - including folders
>
> We can only build on experience with realurl. We experienced long
> generation times for links in another project (typically > 25ms, which
> is not feasable for long lists). We tried with either the Fluid
> <f:link.action> - Viewhelpers or directly from the code with the
> UriBuilder-class with same results. In the end we had to implement our
> own cache for generated links just to speed this up a bit.
>
> Could it be that this had to do with an activated tq_seo?
> Do you have any ideas how to approach this?
> Is cooluri a quicker option?
> How would you do when rewriting that on your own? (we were thinking of
> a DB-table with pageUid, plugin, controller, action & parameters to
> generate links and a backend module that saves Apache-redirection
> (internal, not via HTTP-Status) rules into .htaccess as a sleek
> solution)
>
> Thank you for your input!
>
>
> Regards,
> Jonas
>
> _______________________________________________
> TYPO3-performance mailing list
> TYPO3-performance at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-performance


_______________________________________________
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

wpUDBQFUjra8pp0IwsibV8MBCMVTBACWYR3By0Im6+o9L37MGN2DQY5ZvcdiZTqn
Tqu2sJolqG6uK4sNvLQERgTqKPjFleHVczcM9AopIcrSbKou2H4vvBDvWVhSeIKQ
jhg0ajw0CBaMYZ1CeqeGAMnCpmZLWaX58LPtOeIkMuT1+kjcHnzUKeJ2L8ntjkKu
2KsffcFY3Q==
=Doyh
-----END PGP SIGNATURE-----