Sun 04 Jun 2006 |
| New functionality in 1.0.9 to fix MOSImage performance issue |
| Sunday, 04 June 2006 21:27 |
A performance issue was discovered in the 1.0.x series regards the MOSImage manager when editing Content Items.
Basically the greater the number of images stored in the /images/stories/ directory, the slower the create/edit page for 'Content Items` will take to load. The number of images where this starts to really affect the load time of the page is about 1000 images.
To solve this issue you can now set the /images/stories/ directories that will be available for a content item belonging to a particular Section or Category.
This is accessed by editing a Section or Category, by default all directories are available. By allowing users to select which directories to load for the MOSImage manager, it means one can reduce the number of images loaded for a paricular content item, improving load times.
The problem is not affected by the size of the images stored, just the total number of images. This is because the way the MOSImage Gallery works is that each image, requires a line of html javascript, thus the greater number of images you have, the greater the html required to generate the page.
This can be best demonstrated by the list below: On a default install, the edit content page, the page size is about 35 kbThe original bug report can be found here. Note: in 1.5.x Johan has implemented a more user friendly image insertion mechanism that means this issue does no longer exists in 1.5.x - backward compatability for the use of {mosimage} is still being addressed |