HELP! DB Calls BURYING my host's database server

Author Message

Matthew Knell

Wednesday 06 August 2003 8:58:58 am

EzPublish's database calls, when used by more than one person at a time, are burying my host's MySQL server - is there any way to help this at all? Are their components that make DB calls that I can take out? Is there any way I can make this run more efficiently? I'm three days from launch, and I can't put this out there like this - it'll completely hose the site!

Thanks for your help in advance -

Björn Dieding@xrow.de

Sunday 10 August 2003 2:32:58 pm

Some of the calls are nessary... You can try to boost your system by activating the cache and using cached blocks... the phpA helps a lot too

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Tony Wood

Monday 11 August 2003 1:11:12 am

Matthew,

What version are you using, have you made any specific extension?

We have found that mysql accounts for about 3% of the system activity, so it should not cuase this problem. Ask you ISP for statistics as the what exactly is going worng.

Some advice
1. Use persistant database connection
2. php accelerators will help, but it depends if your host will let you run then. Are you shared, CoLo, managed?
3. Add indexes to mySQL maybe they are missing

I hope this helps

Tony

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 31 2025 01:24:34
Script start
Timing: Jan 31 2025 01:24:34
Module start 'layout'
Timing: Jan 31 2025 01:24:34
Module start 'content'
Timing: Jan 31 2025 01:24:34
Module end 'content'
Timing: Jan 31 2025 01:24:34
Script end

Main resources:

Total runtime0.0275 sec
Peak memory usage6,144.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0064 588.3828151.2422
Module start 'layout' 0.00640.0042 739.6250220.7500
Module start 'content' 0.01060.0153 960.3750997.8672
Module end 'content' 0.02600.0015 1,958.242233.9922
Script end 0.0274  1,992.2344 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.003111.1674140.0002
Check MTime0.00113.9501140.0001
Mysql Total
Database connection0.00134.632010.0013
Mysqli_queries0.00269.491330.0009
Looping result0.00000.061610.0000
Template Total0.00113.910.0011
Template load0.00083.008710.0008
Template processing0.00020.880610.0002
Override
Cache load0.00062.030110.0006
General
dbfile0.003412.329180.0004
String conversion0.00000.029540.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs