[TYPO3-dev] typolink generation high parsetime

[Popy]

And why not to implement a result cache ? For example, creating a function
"isPageAccessible" wich will check only one time if the page is accessible ?

2007/10/25, Martin Kutschker <Martin.Kutschker at n0spam-blackbox.net>:
>
> Bartosz Aninowski schrieb:
> >> we did experience the same for a project.
> >> A lot of time indeed goes into link generation and
> >> we have decided in the end to make a link cache
> >> in our application before we request a link from typo3.
> >
> > Can you share how?
> >
> >> What exactly do you want to disable?
> >
> > Dmitry
> > I want to disable this
> > Query       SELECT *
> >                         FROM pages
> >                         WHERE
> >                                 uid=82 AND pages.deleted=0 AND
> > pages.hidden=0 AND (pages.starttime<=1193318400) AND (pages.endtime=0 OR
> > pages.endtime>1193318400)  AND NOT(pages.t3ver_state=1) AND
> > pages.doktype<200 AND (pages.fe_group='' OR pages.fe_group IS NULL OR
> > pages.fe_group='0' OR (pages.fe_group LIKE '%,0,%' OR pages.fe_groupLIKE
> > '0,%' OR pages.fe_group LIKE '%,0' OR pages.fe_group='0') OR (
> pages.fe_group
> > LIKE '%,-1,%' OR pages.fe_group LIKE '-1,%' OR pages.fe_group LIKE
> '%,-1' OR
> > pages.fe_group='-1'))
>
> Maybe it's faster to do a simple read based on the uid and let PHP do the
> checks. This way Mysql doesn't need to parse that query again an again,
> but
> PHP may be accelerated with an OP code cache.
>
> Masi
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
>



-- 
Popy

Vulnerant omnes, ultima necat.

http://popy.sytes.net