What is difference between Full Page Catch (FPC) and Magento inbuilt caching?
Why we use FPC when already a caching system is available in Magento?
Which one is preferable?
With FPC complete page is cached and hole punching(container) system where by containers are replaced with complete html if needed.
In simple cache system blocks are cached and only blocks are checked if there cache exist.
with FPC on times application will not be initialized but complete page might be delivered from FPC which is not the case with normal block caching.
Related
Using Joomla System - Page Cache, my webpage is now around 4-5 sec.
But i have few pages which will be shown only to registered users. I just checked its taking around 10-15 sec. When i inspected using chrome, i can see few things, i have livechat, which is taking around 2 sec, and few things. But live chat is showing in homepage also. but that page is speed.
Wanted to know is Joomla system cache plugin will not work for registered users visible page. or any other plugin i can use to speed up this type of pages.
Joomla have one JCH Optimize plugin which will decrease your website load speed.
It will compress all css and js file into one file.That file will store in cache so website speed will be up.
This plugin will be helpful to you.
Thanks
Are you using Joomla.
for some components only had the problem of page cache. if u need to clear cache.
and you need to speed up the joomla site
follow the basic step:
Enable Gzip Compression
Using the Gzip Compression feature, you can compress your website pages before sending them to the user. After that, they will be uncompressed by the user’s browser. And this process takes less time than transferring uncompressed pages.
Enable Cache System
Optimization Settings (Images, CSS, Java Scripts…)
Now Check Your Joomla Website Speed
it may use full to speed up your site.
Wanted to know is Joomla system cache plugin will not work for registered users visible page.
Per the Joomla! Documentation, Page Caching:
Only caches pages for guest visitors (not for logged in visitors)
or any other plugin i can use to speed up this type of pages.
Aside from JCH Optimize (which was already mentioned), another component I recommend is JotCache, which is far better than just the Joomla! default cache.
You may, also, use GTmetrix to analyze your site against both Google PageSpeed and Yahoo! Yslow.
Finally, you may try using a CDN to speed up resource delivery. Here are a few:
MaxCDN
Amazon CloudFront
Azure CDN
CDN77
CDNetworks
CDNlion
CacheFly
EdgeCast Networks
KeyCDN
SkyparkCDN
You can use CDN for Joomla! to incorporate the CDN technology.
Overall, your best bet is going to be a combination of the CDN and JCH settings to trim down the overall weight of the site using GTmetrix to compare the site after each change.
Further reading: Joomla Performance & Speed
I'm helping friends with their blog, their admin panel is incredibly slow. After testing all the plugins, I saw that W3 Total cache was responsible of this slowness, more precisely the Object cache option. If I disable this option, the admin runs normally, so does the front of the website.
So, why don't I simply disable W3 Total Cache ?
When I do this, some content disapear from the homepage, some text changes...
I'm not sure how Object caching is working, so my question is : Why ? How can I fix this ?
W3 Total Cache tries to speed up the front end of the website by generating and caching HTML responses for each page. As a user requests a page, it is not processed by the bulk of the PHP that makes up wordpress and is quickly served a cached html page.
If the site is large, and the plugin isn't tuned correctly, it can dramatically slow down the admin side (which is run by PHP and not cached by the plugin).
To fix this, you will have to find the right balance on how often certain pages / post types are cached. If the site isn't a busy one, or if speed is not an issue (I can't see how speed wouldn't be an issue but that's an opinion) you are safe to remove the plugin.
W3 Total Cache has some good information on helping someone determine the settings that should be used. Use that info, along with page view stats to figure out your next steps.
I've built magento website but without full cache and lesti FPC cache the site is very slow, from time to time i need to clean the cache in the website to reveal changes to the catalog, is there a way to generate the cache after the cleaning except with building a basic crawler that scraps the whole website that loads every page so that next time it will be loaded from cache
This is covered in a Stackoverflow thread over here: Magento FPC Cache Warm with user groups, wget, Lesti FPC
I don't think you have much option other than to build your own cache warmer. The thread highlights different types of cache you may have/need.
As we all really know, there appears a little problem with Magento 1.8.x and Varnish. Magento team added the support "form_key" for the most the frontend forms and actions. It is really great, everyone should keep safety first. However it causes a problem with FPC systems as Varnish (great article about this is here http://www.supportdesk.nu/blog/110-magento-1-8-form-keys-impact-on-fpc). Many FPC systems on Magento solves it by putting a placeholder and replace "form_key" during loading a page from cache. It's good for PHP systems that are integrated into Magento , but not for external systems as Varnish. So my question is as follows:
Is there a good enough solution for using FPC as Varnish and Magento 1.8.x?
I consider follows
1) prevent using of the "form_key" on frontend, there are many way to do this (e.g: https://bitbucket.org/supportdesk_nl/turpertine-formkey-workaround/src/574ff1851618dc0e76e4274001fbf3efb89c99f6/app/code/community/SupportDesk/CartFormKey/Model/Observer.php?at=master). However this is hack and is not good generaly. Moreover could be a security risk? What do you mean about this?
2) load the "form_key" via AJAX and replace all links and form inputs by JavaScript code. I'm not sure that it is technicaly realizable (e.g: replacing code snippets like onclick="setLocation('....&form_key=XXX');" would be too difficult) and it will causes too many problems and incompatibilities with various extensions.
3) do not use Varnish. Yes it would be a solution, but let's avoid them for now, please.
4) Your suggestions ???
Many thanks for your answers.
Which FPC are you trying to use anyway? We use Lesti FPC (with Redis Cache backends, and session backends) with Varnish and it works fine.
I don't know if you've properly read one of the links you posted, but Lesti FPC is already patched via this commit, 5 months ago.
I'm seeing some strange behavior on my product pages when trying to view/submit reviews. The review page has essentially the same information as the product page (just styled a bit funny).
We have applied many caching related performance improvements to Magento. We are using APC, Varnish with the PageCache extension, Fooman Speedster, and have added the product and category blocks into the Magento cache.
I'm fairly certain I need to do something with one of these caches, but I'm not sure what. Is it the block caching? Varnish?
Anyone experienced this and have any suggestions?
Well, the easiest way to isolate the issue would be to disable your caches 1 by 1.
Also, a URL might help ...