RE: ORM doctrine

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Peter Lind [mailto:peter.e.lind@xxxxxxxxx]
> Sent: Sunday, December 12, 2010 3:05 AM
> To: Tommy Pham
> Cc: Lester Caine; php-general List
> Subject: Re:  ORM doctrine
> 
> On Sunday, 12 December 2010, Tommy Pham <tommyhp2@xxxxxxxxx>
> wrote:
> >> -----Original Message-----
> >> From: Lester Caine [mailto:lester@xxxxxxxxxxx]
> >> Sent: Sunday, December 12, 2010 2:10 AM
> >> To: php-general List
> >> Subject: Re:  ORM doctrine
> >>
> >> Peter Lind wrote:
> >> > Your posts seem to indicate that caches are only useful when other
> >> > parts of the app have been done wrong. My point was that this is a
> >> > fairly fundamental misunderstanding of caches - regardless of what
> >> > you are or aren't capable of optimizing.
> >>
> >> CHACHES are only useful when there are static views of the
> >> information available. Only static elements can be cached with any
> >> real chance of performance improvement, so part of what Tommy is
> saying is correct.
> >> Although the way he has worded that is perhaps a little misleading?
> 
> Possibly. However, thinking that a cache is something you apply at the end
> of development means you may well bar yourself from better uses of one.
> Ie. thinking that a cache is "icing on the cake" prohibits you from "mixing it
> into the cake" (to further abuse a metaphor) which could give you "a better
> recipe".

I'm not sure about being 'a better cake' with all that sugar, you'll have a higher chance of diabetes.  Therefore in trying to achieve a healthy (lean & mean) app, you'll more chances of having problems than it intend to solve.

Regards,
Tommy

>  I may have misunderstood the topic, but a cache to me is more than just
> storing views. It's also the db cache, memcache, apc, etc. You have to think
> about how you use these - some of them can't just be slapped on to your
> app after development.
> 
> 
> >> Data caching SHOULD always be the
> >> domain of the database, so duplicating that in PHP is pintless.
> 
> So you're saying one should never use memcache for storing data from the
> db?
> 
> Regards
> Peter
> 
> --
> <hype>
> WWW: plphp.dk / plind.dk
> LinkedIn: plind
> BeWelcome/Couchsurfing: Fake51
> Twitter: kafe15
> </hype>


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux