Are you making a single eshop for just one store, or are you planning on your eshop being distributed to a zillion users?...
Cuz unless your store gets a MILLION hits, the generation of static HTML instead of just using PHP will probably not save you very much at all. Write the application the most straight-forward way you can, and then check for acceptable performance. If it's not acceptable, use valgrind or xdebug to find the bottleneck, and fix it. Repeat this step until performance is acceptable. Trying to "fix" your performance before you know what the bottleneck is, is almost always a complete waste of time/resources. On Sun, February 25, 2007 4:49 am, Martin Zvarík wrote: > Hi, > I am making an eshop and I am thinking about caching system. > > You understand, that it cannot be entirely cached because visitor has > it's own shopping cart etc. > > So, my thought is to cache only few blocks like "Categories", > "Navigation menu" etc. by storing it to an HTML file. > > The advantages are that it doesn't have to query database and generate > the HTML code again, but my question is: Is it good approach? > Shouldn't > we optimize database instead of restoring the data on harddrive? > > Thank you for ideas, > Martin Zvarik > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some starving artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
