MySQL Runtime Information: Handler_read_rnd_next very high

«

Previous topic

|

|

Next topic

»

Author	Message
Martin Burger	Saturday 18 November 2006 5:50:34 am Hello! I checked the runtime information of a MySQL instance that hosts databases for eZ publish. The variable "Handler_read_rnd_next" is very high (relative to the number of visits): 3 M The description of phpMyAdmin says: "The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have." So, why does eZ publish cause a lot of table scans? Or, is any index missing? Regards, Martin http://www.netbeyond.de/
André R.	Sunday 19 November 2006 4:22:29 am This depends on what eZ Publish version you are running. There where some added indexes in the 3.8 and 3.8.4 versions eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Martin Burger	Sunday 19 November 2006 7:33:43 am We are bound to 3.6.11 because we use Debian stable which provides only PHP 4.3.10 as package. Which indexes were added? Can I add them manually for version 3.6.11? http://www.netbeyond.de/
André R.	Monday 20 November 2006 12:52:13 am The indexes that where not 3.8 specific went into 3.6.9: http://pubsvn.ez.no/nextgen/stable/3.6/update/database/mysql/3.6/dbupdate-3.6.8-to-3.6.9.sql I guess you have added these indexes, so could you make a issue on this ? http://issues.ez.no eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom

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 00:23:23
Script start
Timing:	Jan 31 2025 00:23:23
Module start 'layout'
Timing:	Jan 31 2025 00:23:23
Module start 'content'
Timing:	Jan 31 2025 00:23:23
Module end 'content'
Timing:	Jan 31 2025 00:23:23
Script end

Main resources:

Total runtime	0.0264 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0056	588.3828	151.2422
Module start 'layout'	0.0056	0.0039	739.6250	220.7500
Module start 'content'	0.0095	0.0153	960.3750	1,001.8359
Module end 'content'	0.0248	0.0016	1,962.2109	33.9922
Script end	0.0264		1,996.2031

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	11.5442	14	0.0002
Check MTime	0.0013	4.8737	14	0.0001
Mysql Total
Database connection	0.0009	3.3569	1	0.0009
Mysqli_queries	0.0022	8.1620	3	0.0007
Looping result	0.0000	0.0452	1	0.0000
Template Total	0.0011	4.3	1	0.0011
Template load	0.0009	3.5051	1	0.0009
Template processing	0.0002	0.8103	1	0.0002
Override
Cache load	0.0007	2.5159	1	0.0007
General
dbfile	0.0016	5.9442	8	0.0002
String conversion	0.0000	0.0307	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs