ez with big web site

Saturday 25 November 2006 2:41:16 am

1)Image storage
It will be usefull to change the storage dir for big web site.
Actually when I upload a image, the url contains :
/myfolder/myfolder2/imgname.png
Maybe it's a nice way to find it on the drive and for google but
if i have hundred of folder on ez, I will have hundred of directory on my filesystem.
Just try to list a directory with millions of file or folder ....

Maybe it'll be a go way to store file like the cache files:
url will be /0/1/4/aaa.png

2) static cache
I have the same trouble with the static cache.
the static cache, create on folder and one index page for each nodes.
with this system, it's easy to configure apache to find the good page, but what happen if I have a folder with 10000 object ,I will have 10000 directory on my disk with 1 file in each folder.
Why don't you use the same way of the cache file?

don't flush the cache

Tuesday 28 November 2006 2:48:47 pm

So what the limit of ez (not only for the storage but for the number of object EZ could manage)
How many users/objects (small object with 10 or less attributes and big object with 20 attributes) ez will manage?

I don't think I need to have millions of images to have a bug with the filesystem.
Just try to list a directory when you have more than 10000 sub folders.

How do you manage your 50000 post? do you use special extension?

Thanks for your answer.

don't flush the cache

Wednesday 29 November 2006 1:07:21 am

Just to clearify: eZ does not say that the limit of eZ publish is 250 000 objects.

The eZ publish 3.8 package was tested with 2 million objects and it worked fine.

The performance and number of objects is no an exact science though. It does depend on the design of the content architecture. If you e.g. have all the objects in the same folder you get performance issues with sorting when you have large amount of objects under one node. It does also depend on the structure of your content classes. Some setups are heavier than others. So, to know the limitations of your setup you need to test for this.

Our testing was done with the standard content class setup in eZ publish. We created folders with 5 000 articles in each folder using a 3 level hierarchy.

Cheers,

-bård

Documentation: http://ez.no/doc

Friday 26 January 2007 11:32:44 am

Just for information ez publish work great with 400000 object (4 M lines in the ezcontentobject_attribute table)

We just have to change the user system and it'll be great...

don't flush the cache