Re: DB_DataObject performance

On Fri, 2005-10-28 at 22:21 +0200, Olivier Guilyardi wrote: > Hi, > > I've had successful experiences using DB_DataObject on corporate intranets, with > a few dozens of users. But I'm currently working on a website which may soon > receive about 30000 hits a day (latest evaluation). guess 3000 hits per hour (assuming squashed in 10 hour period) =~50 hits per minute.. if you run ab (apache benchmark) - ab -c 30 -n 100 http://yoursite/a_page_that_may_be_slow.php you should see how it copes with 100 requests, 30 concurrently - if it responds in less than 60 seconds, you should be OK... My guess is that would be no problem, the bigger bottleneck (as previously mentioned) is optimizing your queries - run with debugging on, and see if you really need to fetch all the data it is fetching - or if you are fetching the same data multiple times.. (rather than caching the results..) Regards Alan > > Have any of you already used DB_DataObject on high traffic websites ? > Is there any serious CPU and Memory usage benchmarks out there ? > > Here's the implementation choice I'm facing : > - either use DB_DataObject which relies on DB, DB_Result, etc... > - or code my own dataobjects which simply encapsulate mysql_* calls > > Wether I choose the first or second option, I'll stick with the "dataobject > design pattern" as a way to encapsulate the sql code and other smart behaviours. > > -- > og >