eZPublish benchmarking

Previous topic

Developer

Next topic

Author	Message
Damien Pitard	Friday 18 July 2008 3:23:34 am Hi, We are going to benchmark different clustered filesystems to replace our storage database which is over stress due to big audience on our site. Does anybody have some scripts to put an eZpublish system under stress... especially concerning filelocks? Thx Damien Damien Pitard \| Prisma Presse
André R.	Wednesday 23 July 2008 7:44:55 am Since there is no point in requesting css / images when testing file locks, you can easily use ab (apache bench): http://httpd.apache.org/docs/2.2/programs/ab.html Note, stat calls are one of the focus points in 4.1, to improve performance on windows / os x / nfs and other clustered file systems. One patch for 4.x that are awaiting approval might interest you (so you get a idea of how 4.1 will work): http://issues.ez.no/IssueView.php?Id=12137&activeItem=5#comment257136 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

Author

Message

Damien Pitard

Friday 18 July 2008 3:23:34 am

Hi,

We are going to benchmark different clustered filesystems to replace our storage database which is over stress due to big audience on our site.

Does anybody have some scripts to put an eZpublish system under stress... especially concerning filelocks?

Thx

Damien

Damien Pitard | Prisma Presse

André R.

Wednesday 23 July 2008 7:44:55 am

Since there is no point in requesting css / images when testing file locks, you can easily use ab (apache bench):
http://httpd.apache.org/docs/2.2/programs/ab.html

Note, stat calls are one of the focus points in 4.1, to improve performance on windows / os x / nfs and other clustered file systems.

One patch for 4.x that are awaiting approval might interest you (so you get a idea of how 4.1 will work):
http://issues.ez.no/IssueView.php?Id=12137&activeItem=5#comment257136

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

eZ debug

Timing:	Jan 31 2025 03:38:11
Script start
Timing:	Jan 31 2025 03:38:11
Module start 'layout'
Timing:	Jan 31 2025 03:38:11
Module start 'content'
Timing:	Jan 31 2025 03:38:11
Module end 'content'
Timing:	Jan 31 2025 03:38:11
Script end

Main resources:

Total runtime	0.0269 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0055	588.1250	151.2109
Module start 'layout'	0.0055	0.0046	739.3359	220.6719
Module start 'content'	0.0101	0.0150	960.0078	997.7578
Module end 'content'	0.0251	0.0017	1,957.7656	29.9922
Script end	0.0268		1,987.7578

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	10.7220	14	0.0002
Check MTime	0.0012	4.3603	14	0.0001
Mysql Total
Database connection	0.0009	3.2638	1	0.0009
Mysqli_queries	0.0031	11.4902	3	0.0010
Looping result	0.0000	0.0559	1	0.0000
Template Total	0.0012	4.6	1	0.0012
Template load	0.0009	3.4714	1	0.0009
Template processing	0.0003	1.1018	1	0.0003
Override
Cache load	0.0007	2.4787	1	0.0007
General
dbfile	0.0028	10.2518	8	0.0003
String conversion	0.0000	0.0293	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