eZ performance with a large number of users

Next topic

Author	Message
Marko Žmak	Wednesday 24 June 2009 2:00:55 am I have to setup an eZ site which has a large number of users (>40.000). Besides standard fields, each user has a phone number attribute that can be searched for in eZ. So I would like to know how will this large number of users affect: - performance of user login? - performance when doing fetch for users based on attribute filter for the phone number attribute? Does someone have experience with similar number of users? How much difference in performance is between the number of 40.000 users and for example 2000? Also, how much would a custom fetch operator that is specialized for retrieving users based on phone number improve the preformance? P.S. I'm using eZ 3.10.1 and mysql database. -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
John Moritz	Wednesday 24 June 2009 6:09:20 am as far as i know, ezPublish can handle more than 1.000.000 Objects without problems. A ezuser is just a object, so 40.000 will be no problem. Your bottleneck will be the Serverbandwith, respectivley how many users you have online at the same time. For this, ezPublish has cluster functionalities!
Gaetano Giunta	Wednesday 24 June 2009 6:21:15 am The main problem you will find having a number of users in the order of magnitude of 100.000 is the usability of the admin interface: if they are all part of the same group, navigating it becomes a pain, and you will have to resort to search for users or build a custom interface to easily find them. Storing them in folders by first letter of login might also be an idea. Login is not a problem. Heavy customization of the site based on user profile is a scalability brake anyway, even with few users: avoid having to fetch the user object on every page if you can. Take care if putting the user id in cache block keys: you will generate a lot of those files. Principal Consultant International Business Member of the Community Project Board

Author

Message

Wednesday 24 June 2009 2:00:55 am

I have to setup an eZ site which has a large number of users (>40.000). Besides standard fields, each user has a phone number attribute that can be searched for in eZ. So I would like to know how will this large number of users affect:

- performance of user login?
- performance when doing fetch for users based on attribute filter for the phone number attribute?

Does someone have experience with similar number of users?
How much difference in performance is between the number of 40.000 users and for example 2000?
Also, how much would a custom fetch operator that is specialized for retrieving users based on phone number improve the preformance?

P.S. I'm using eZ 3.10.1 and mysql database.

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

John Moritz

Wednesday 24 June 2009 6:09:20 am

as far as i know, ezPublish can handle more than 1.000.000 Objects without problems. A ezuser is just a object, so 40.000 will be no problem.

Your bottleneck will be the Serverbandwith, respectivley how many users you have online at the same time. For this, ezPublish has cluster functionalities!

Gaetano Giunta

Wednesday 24 June 2009 6:21:15 am

The main problem you will find having a number of users in the order of magnitude of 100.000 is the usability of the admin interface: if they are all part of the same group, navigating it becomes a pain, and you will have to resort to search for users or build a custom interface to easily find them. Storing them in folders by first letter of login might also be an idea.

Heavy customization of the site based on user profile is a scalability brake anyway, even with few users: avoid having to fetch the user object on every page if you can.

Take care if putting the user id in cache block keys: you will generate a lot of those files.

Principal Consultant International Business
Member of the Community Project Board

eZ debug

Timing:	Jan 18 2025 16:24:29
Script start
Timing:	Jan 18 2025 16:24:29
Module start 'layout'
Timing:	Jan 18 2025 16:24:29
Module start 'content'
Timing:	Jan 18 2025 16:24:30
Module end 'content'
Timing:	Jan 18 2025 16:24:30
Script end

Main resources:

Total runtime	0.6912 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	588.0469	152.6406
Module start 'layout'	0.0057	0.0039	740.6875	39.4766
Module start 'content'	0.0096	0.6801	780.1641	581.1953
Module end 'content'	0.6897	0.0015	1,361.3594	12.1250
Script end	0.6912		1,373.4844

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.4634	16	0.0002
Check MTime	0.0014	0.1956	16	0.0001
Mysql Total
Database connection	0.0009	0.1240	1	0.0009
Mysqli_queries	0.6414	92.7938	59	0.0109
Looping result	0.0006	0.0923	57	0.0000
Template Total	0.6611	95.6	2	0.3305
Template load	0.0019	0.2681	2	0.0009
Template processing	0.6592	95.3681	2	0.3296
Template load and register function	0.0001	0.0133	1	0.0001
states
state_id_array	0.0011	0.1620	1	0.0011
state_identifier_array	0.0008	0.1230	2	0.0004
Override
Cache load	0.0015	0.2102	20	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0910	3	0.0002
Fetch class attribute name	0.0015	0.2190	5	0.0003
XML
Image XML parsing	0.0013	0.1861	3	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0013	5	0.0000
General
dbfile	0.0009	0.1335	24	0.0000
String conversion	0.0000	0.0013	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 14 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs