Optimize utility

[Scho]

This gives choices for defrag EE database and optimize EE database. When and why should these be used?

[Pekka]

Defragment is identical to disk defragment tool found in most operating systems. MySQL holds all data as disk files, and it most of the time reads disk with every query. That is why on big databases disk sector format fragmentation may cause some slowdown. Fragmentation is result of deleting records or tables. EE does a lot of internal housekeeping after delete commands, so generally this command is not needed. But as databases are often on shared machines there are lot of other activities which can change disk structure.

Optimize command rebuilds table indexes. If you encounter _extreme_ slowdown, this command may help you gain back the original speed. Indexes can be lost during restore with some odd tools (though EE Backup does index optimization automatically after restore), or when empty tables are re-created for some reason.

Normally EE does not need these commands, so apply them only if you suspect above problems or instructed by me.

SPEED TIP: EE gets a speed kick from data complexity - this means that you should have let's say at least 5 photographers, 5 workflows, 5 accessories, 10 locations, 5 cameras, 5 lenses, 7 photos, 2 exhibitions. When you have at least those on your database (they do not need to be in use, just exist) MySQL starts to use more sophisticated features in EE database, and run mainly on RAM.

[Scho]

Pekka - Thanks for the explanation and the additional speed tips. My site still seems slow, but that may simply be due to my host server provider and not EE.

[Pekka]

Scho wrote:
Pekka - Thanks for the explanation and the additional speed tips. My site still seems slow, but that may simply be due to my host server provider and not EE.

Yes, to me it looks like the server has slight trouble sending images out. EE builds list page in less than .4 seconds there, photo pages in about 0.1 sec. and the rest is plain old html (html code download, image retrieve).

Some of your image files are quite big in file size - even on this server the speed increase is noticeble when you downsize photos and drop serving large ones (only in private) - a server pipe can get full easily with few large size downloads at the same time.

And great images btw.

[Scho]

Thanks for checking Pekka. I'll try to keep my file size down. If I turn off Large size path in photo editor, so it is not available for display in browser, will the Large file size path still be available in ee_commerce for print serving?

[Pekka]

Scho wrote:
Thanks for checking Pekka. I'll try to keep my file size down. If I turn off Large size path in photo editor, so it is not available for display in browser, will the Large file size path still be available in ee_commerce for print serving?

Yes.