Are several thousand locations a problem?

Next topic

Author	Message
Bertin Hansen	Monday 15 November 2010 4:33:58 am I am working with a large food recipe site and the customers of that site are able to bookmark recipes and organize them in self-made categories ("folders") on their own cooking booke page. The standard bookmark feature does not support categorization so I am planning to use the location feature of eZ Publish to solve this requirement. When the user creates a new category, the code will create a new folder under the customers cooking book node (my own class), and when the customer bookmarks a recipe the code will add a new location to the recipe to that new folder. We will have thousands of users, so a recipe may be located in several thousand locations. Will this be a performence problem? Is this a good idea, or could the requirement be solved in another way? I have rejected the idea of using a object relation list, because I think this would give bad performance when editing the recipe in the Admin GUI.
Bertrand Dunogier	Monday 15 November 2010 5:22:48 am I wouldn't use locations for that. Locations are strongly linked to content cache, and this would really hurt when updating a recipe... Relations might be a way to go, you just have to write a custom UI for it. Pretty much like you wouldn't use the default UI to add locations, would you ? Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Gaetano Giunta	Monday 15 November 2010 6:12:10 am Maybe the keyword datatype can also be used with some kind of namespaced keywords? It also has some knobs related to caching that can be of use... Principal Consultant International Business Member of the Community Project Board

Author

Message

Monday 15 November 2010 4:33:58 am

I am working with a large food recipe site and the customers of that site are able to bookmark recipes and organize them in self-made categories ("folders") on their own cooking booke page. The standard bookmark feature does not support categorization so I am planning to use the location feature of eZ Publish to solve this requirement. When the user creates a new category, the code will create a new folder under the customers cooking book node (my own class), and when the customer bookmarks a recipe the code will add a new location to the recipe to that new folder. We will have thousands of users, so a recipe may be located in several thousand locations. Will this be a performence problem? Is this a good idea, or could the requirement be solved in another way? I have rejected the idea of using a object relation list, because I think this would give bad performance when editing the recipe in the Admin GUI.

Bertrand Dunogier

Monday 15 November 2010 5:22:48 am

I wouldn't use locations for that. Locations are strongly linked to content cache, and this would really hurt when updating a recipe...

Relations might be a way to go, you just have to write a custom UI for it. Pretty much like you wouldn't use the default UI to add locations, would you ?

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier

Gaetano Giunta

Monday 15 November 2010 6:12:10 am

Maybe the keyword datatype can also be used with some kind of namespaced keywords? It also has some knobs related to caching that can be of use...

Principal Consultant International Business
Member of the Community Project Board

eZ debug

Timing:	Jan 29 2025 23:45:55
Script start
Timing:	Jan 29 2025 23:45:55
Module start 'layout'
Timing:	Jan 29 2025 23:45:55
Module start 'content'
Timing:	Jan 29 2025 23:45:55
Module end 'content'
Timing:	Jan 29 2025 23:45:55
Script end

Main resources:

Total runtime	0.0354 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0058	588.2656	151.2266
Module start 'layout'	0.0058	0.0023	739.4922	36.6875
Module start 'content'	0.0081	0.0257	776.1797	90.2031
Module end 'content'	0.0337	0.0017	866.3828	33.9766
Script end	0.0354		900.3594

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	7.2350	14	0.0002
Check MTime	0.0010	2.9312	14	0.0001
Mysql Total
Database connection	0.0008	2.4000	1	0.0008
Mysqli_queries	0.0022	6.1303	3	0.0007
Looping result	0.0000	0.0343	1	0.0000
Template Total	0.0012	3.4	1	0.0012
Template load	0.0009	2.4734	1	0.0009
Template processing	0.0003	0.8779	1	0.0003
Override
Cache load	0.0005	1.5248	1	0.0005
General
dbfile	0.0189	53.4028	8	0.0024
String conversion	0.0000	0.0209	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