Re: Rapid Developement / Bloated Product?
I have been looking into using cake for a few projects, and performance related issues are exactly what I am worried about... Would it be not possible to cache certain data/metadata at runtime once you are in production mode (and not in dev mode) such as mysql metadata. Some other things I can think of is parsing and caching layout templates, information on views, metadata information about probably controllers/helpers/models/etc using lazy caching (cache as you go). One more thing that worried me was the fact that caching system was built-into the core and that it is not replacable. For example, I want to use memcached which is way waster than using php files for caching, and for that it looks like I need to go into core and hack it, which is the last thing I want to do... On Jan 14, 12:35 pm, "eagerterrier" <[EMAIL PROTECTED]> wrote: I've been using cake for about 3 weeks now (extremely intensively), and it is a marvellous tool for developing sites quickly and being able to divide work up between developers in a logical way.However, with speeds at a *minimum* of 0.2 seconds per page regardless of what's on them, I am concerned. The current site which I am revamping has at present *maximum* speeds of 0.03 seconds for the home page, and it needs to be this tight because it is a high traffic site (2m+ PIs per month). And although I'm pleased to see that CakePHP version 1.2 has stopped carrying around 1Mb+ of repeated information in arrays, its processing speed is still on the slow side. What I'm looking for is a way of altering bootsrap and basics (which appear to be the main culrpits -http://www.cakephp.org/profile.png) to bypass some of this processor intensive stuff and replace it with static text (for example, setting up a flat file of arrays of my SQL table structure rather than cake looking for it the whole time). Does anyone know how to go about this? I have presently only been looking into *how* CakePHP works (to get my project up to speed), and not *why* it works, so I would be grateful for the Cake aficionados to point me in the right direction. Perhaps I'm missing something and in the same way that you have the bake function, you might also have a 'decorate' function that would do what I am asking, but I can't find it anywhere and I am losing sleep over the site performance. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Caching in CakePHP?
Hi, As far as I can see from the documents, caching is handled automatically by CakePHP for a specific controller+view combo, and cake uses files to cache full view data. Is it possible to overwrite this behavior such that, I will be able to cache parts of a page, not all the page. And, also I would like to use memcached for better performance and cache management. Is this something I should do manually or is there a way I can plugin/overwrite caching mechanism in a clean way? Thanks. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Modular Design?
Hi All, I am new to CakePHP and have a question regarding modular coding in cake. Basically, let's say I am implementing a bookstore, and I want to have a generic layout that will be used throughout the pages, which is very easy in CakePHP. Along with that, I would like to have modules (div boxes with specific content coming from the db) that would be shared across the pages, such as most active books , newest items, etc. Now, I can do this with Cake by invoking the relevant model from the controller, and coming up with cake "elements" which take this data. But, as I said, I don't want to include these models over and over on every page that contains this module and want my modules to be totally independent and completely modular, in an encapsulated way that they will have their own model/own controller and own view and I just want to include this as a black box. This is especially important, given that I want to use these modules across pages and do not want to replicate code and/or minimize code replication. Basically, my layout will have "div" areas, and I want to place various "modules" in these divs depending on some configuration, i.e. on main page div1 will have most active books, on some other page, e.g. book view page, I want to place them on div5, and so on. A typical usage of this is the modules concept on Joomla/Mambo... Is something like this possible in CakePHP? Could you please provide suggestions as to how I come up with encapsulated modules like this? Thank you in advance. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
