reducing processor time usage in back-end

[void]

Hello,

first of all, we would like to thank people, who took place at development CMS Made Simple, it's a really good tool to have.

Our question is about processor time usage in back-end. Content is almost full-static and as our humble researches shows that most of processor time is consumed by routines in cms admin panel (add/edit content). Is there any way to correct this situation at a cost of performance? Or could it be improving scalability like splitting admin panel on other server? Or modifying cms events that raises on content adding/editing? Or else?

Site pages: over 1 000.

MySQL is running on remote server.

Site running at:

Code: Select all

CMS version 1.8.1

Modules:

CMSMailer 2.0
FileManager 1.0.2
MenuManager 1.6.5
ModuleManager 1.4
nuSOAP 1.0.1
ThemeManager 1.1.1
EditArea 0.2.9
Play 1.0.3
Captcha 0.4.1
Smileys 0.2.0
News 2.10.6
Guestbook 1.1.12
TinyMCE 2.7.2


Configuration info:

php_memory_limit: 64M 
process_whole_template: false 
output_compression: false 
max_upload_size: 256000000 
default_upload_permission: 664 
url_rewriting: mod_rewrite 
page_extension:  
query_var: page 
image_manipulation_prog: GD 
auto_alias_content: true 
locale: ru_RU 
default_encoding: utf-8 
admin_encoding: utf-8 
set_names: true 
debug: false 
use_smarty_php_tags: false 


PHP information: 

phpversion: 5.2.12  
md5_function: True   
gd_version:  2  
tempnam_function:  True 
magic_quotes_runtime:  False  
Is E_STRICT disabled in error_reporting (E_STRICT): disabled
memory_limit: 64M  
max_execution_time:  30   
PHP output_buffering (output_buffering): 4096  
safe_mode: False 
file_uploads: True
post_max_size: 256M  
upload_max_filesize:  256M  
session.save_path (session_save_path): /tmp (1777)  
Sessions are allowed to use Cookies (session_use_cookies): True 
xml_function: True
create_dir_and_file: ok 
PHP register_globals (register_globals): False 
disable_functions in PHP (disable_functions): ok
PHP опция open_basedir (open_basedir): ok
test_remote_url: ok
fsockopen:  OK!  
fopen:  OK!  
ini_set (check_ini_set): True 


Server information: 

server_api: cgi-fcgi  
server_db_type: MySQL (mysqli)  
server_db_version: 5.0.70  


Server software:

Apache/2.2.14 (Unix) mod_fcgid/2.3.5-dev  
server_os: Linux 2.6.28-r9-s-a-1gb Вкл x86_64 

php.ini in attachment.

Thanks.

ps: it could be worst english ever, sorry 

[Peciura]

You could add Feature Request smth like "Filter pages depending on user selected hierarchy". That would display just single menu branch and reduce traffic to mysql server.

[NaN]

A good feature would be pagination like in news article list or gcb list.
So if you have more than 1000 pages in backend it will only show ... lets say 50 per page.
I believe that would increase backend performance a lot.
Also the memory exhausted error if you have lots of pages and all subpages expanded could be reduced if only a specific amount of content items per page would be shown.

But this is not the place to talk about feature requests.

Splitting backend and frontend into several servers sounds interesting.
I've never tried this. But i think there would be a problem with managing files.

Modifiyng the events could also help. But this depends on the amount of events and what scripts are processed on add/edit content.

There are some tuning tips in the forums. Did you already try all these?
(They might be in most cases for frontend only but increase performance might be always a good idea)

http://forum.cmsmadesimple.org/index.ph ... 23244.html
http://forum.cmsmadesimple.org/index.ph ... 809.0.html

[JeremyBASS]

One thing too.. thou I think it'd be nice to have a "Filter pages depending on user selected hierarchy" and "a pagination feature" and even have the admin set up so that it can be split..

You may want to make things less static... I have a few sites that have like 100-300 pages but on the front, it looks like there are like 2000+ pages.  With the fact that there is the cache you will/should see almost no difference in speed on the front after render, thou you will see a difference on the back.  I do know also all dev are working hard to keep finding way to speed things up.

Just some thoughts.. Cheers -Jeremy

[void]

thanks for your answers

to Peciura and NaN:

pagination in admin area could be great (should i post it in feature request or what should i do?)

Tuning tips are great too, thanks. Full cache is an interesting feature, i was already looking for static html export, but for me this solution looks better (in a practical way).

Main problem, which turn me to think about splitting admin area is hoster processor usage limit (5% - 1 core), so i'll try it.

to JeremyBASS:

sorry, i don't understand what do you mean by "With the fact that there is the cache you will/should see almost no difference in speed on the front after render, thou you will see a difference on the back".
Cache slows admin area?

i've already "killed" some db records in cms_content_props, which were blank and didn't come "out of box", it helps 

[JeremyBASS]

to JeremyBASS:

sorry, i don't understand what do you mean by "With the fact that there is the cache you will/should see almost no difference in speed on the front after render, thou you will see a difference on the back".
Cache slows admin area?

i've already "killed" some db records in cms_content_props, which were blank and didn't come "out of box", it helps 

No the cache doesn’t slow the admin area... I was preempting the more dynamic front suggestion which people offend remark on with something like "I need it to be fast" etc... The point is reducing the page count speeds up the back end.. Without knowing what you have for the back, I would think that you could fork a module, may-be news, so have them “create” the pages you’d be removing… cheers -Jeremy

[carasmo]

I really would to also request and help fund the ability to search regular pages by string and -- more importantly -- show only 25-50 pages and so forth with pagination, like news.

I like the cataloger module and many times there's a lot of stuff to catalog and it's hard to manage after awhile.

Where do I post this request?

[Peciura]

Where do I post this request?

http://dev.cmsmadesimple.org/feature_request/list/6

[baresi]

For what it's worth I would love pagination... I posted about it a long time ago http://forum.cmsmadesimple.org/index.ph ... l#msg93352 from the reaction I got back then there was talk that 2.0 (which later became 1.7+) would improve it so I left it at that but also I posted about it in "Help Wanted (commercial)" (which didn't get replies so I just stayed waiting for 2.0 or 1.7, etc.)