Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
worth the set cache html code or just mysql (serialize)?
the full HTML should reduce load time without re-implementation of the php script if I’m wrong. Do you know of some other disadvantages?
//Use html to serialize cache or another option?
Nothing is faster than plain HTML pages, so go for both cache solutions. But as Alfred said, you should use APC instead of MySQL as serialized cache. Also, you should take advantage of the MySQL query cache.
Further on, checkout memcached and/or Redis as alternative for storing values which need to be stored and retrieved very often.
EDIT:
Just another idea to gain more performance – store your HTML files using a tmpfs (RAM based) filesystem. If something is faster than pure HTML files, then it can only be pure HTML files served via RAM disk. 😉