As you say this varies greatly with each application and the hardware setup being measured.
Very generally, I'd say that is you can stay under 100ms for most "normal" data. If you are over 100 and not doing statistical gathering or have a very "saturated" database or something like that you can probably optimize things using either pagination or containment. For most pages any single query rarely reach 50ms. Most are from 1-20 for my sparely populated dev database. I warn you against staring blindly at the query time, trying to get it down. A slow query is almost always faster than a fast query and some kind of data manipulation in php. So don't simplify a query to speed it up and replace that with an extra for-loop or something. Do the opposite :) A note on speed values: I measure these things on my workstation (iMac 2.4ghz). If it is fast enough here it should be good on the server, right. :) On Apr 28, 1:36 am, "Dave Maharaj :: WidePixels.com" <d...@widepixels.com> wrote: > Just wondering what the general feel is for acceptable query times? What is > too high? What's a good range to try to stick to? I know it will differ per > application but just want to see what people use as a general practice. > > Thanks, > > Dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
