Hi,

as far as I known there is also the possibility to cache parts of a site.
Es grüßen die Bergfreunde,

Till

P.S.: Neues gibt's im Blog sowie bei Facebook & Twitter!



Bergfreunde GmbH
Till Voß
Leiter Online-Technik
Bahnhofstraße 26
72138 Kirchentellinsfurt

Telefon: +49 (0)7121 30459-24
Fax: +49 (0)7121 30459-27
E-Mail: t...@bergfreunde.de
Web: www.bergfreunde.de

Sitz der Gesellschaft: Kirchentellinsfurt
Amtsgericht Stuttgart, HRB: 382746
Geschäftsführer: Martin Theben, Ronny Höhn

Am 21.10.2011 um 11:34 schrieb Kai Gazmaga:

> Hi Thomas,
> 
> yes, I know about that, but this is - again - the same thing with sessions. 
> HTML is stored - not in local directory, but on a memcached-service - but we 
> have the same result. As soon as there is a session (user-data somewhere in 
> the full html-document) the cache is useless and we wont get any advantage 
> from it.
> 
> Regards, Kai
> 
> 
> Am 21.10.2011 11:11, schrieb Thomas Neumann:
>> 
>> Hey Kay,
>> 
>> have a look at this module 
>> http://www.syseleven.de/blog/1934/oxid-super-cache-mehr-power-fur-den-shop/
>> 
>> Developed by Fatchip and syseleven... interesting..
>> 
>> Best regards
>> Thomas Neumann
>> smart ecom - eCommerce Consulting
>> 
>> Gustav-Linden-Strasse 23
>> 40878 Ratingen
>> m 0151 / 419 043 13
>> e  tho...@smart-ecom.com
>> 
>> Am 21.10.2011 um 11:08 schrieb Kai Gazmaga:
>> 
>>> Hello everybody,
>>> 
>>> Marco said something about plans of integrating memcached into Oxid CE / PE 
>>> in the future. I currently have a project (Mastershop with PE and some 
>>> further CE-Shops) each with 18.000 articles or more (incl. variants) for 
>>> wich I am looking for some performance-optimisation-Options. The 
>>> HTML-Caching from FatChip does cause some trouble in another project at the 
>>> moment and will not solve the problem of slow response when as soon as a 
>>> session is started. So there must be a way to cache SQL or objects at least 
>>> partly, where heavy DB-load / recursion / many objects have to be generated 
>>> but are not updated too often.
>>> 
>>> http://www.oxid-esales.com/forum/showthread.php?p=63787
>>> 
>>> In this thread we already have the topic, but I do not want a solution that 
>>> is not udateable or find a core-solution a few weeks after i implemented my 
>>> caching. Does anyone have a proper solution or information about a release 
>>> of further caching in future releases? Joscha Krug said something about a 
>>> release in 4.6. Is that relistic?
>>> 
>>> Mit freundlichem Gruß, with best regards
>>> 
>>> Kai Gazmaga
>>> VektorDesign - Online-Shops und Programmierung
>>> Kai Gazmaga 
>>> Katharinenstraße 57 
>>> 73 728 Esslingen    Tel.: +49 711 - 25516226 
>>> Fax: +49 711 - 25518078 
>>> Mail: i...@vektordesign.de 
>>> Web: www.vektordesign.de
>>> _______________________________________________
>>> dev-general mailing list
>>> dev-general@lists.oxidforge.org
>>> http://dir.gmane.org/gmane.comp.php.oxid.general
>> 
>> 
>> 
>> _______________________________________________
>> dev-general mailing list
>> dev-general@lists.oxidforge.org
>> http://dir.gmane.org/gmane.comp.php.oxid.general
> _______________________________________________
> dev-general mailing list
> dev-general@lists.oxidforge.org
> http://dir.gmane.org/gmane.comp.php.oxid.general

_______________________________________________
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Reply via email to