When I use the content manager and wants to save, there are significant differens between the buttons "Submit" and "Apply" in how long time it takes before the green confirmation appears. The difference is not notable when running on local mashine, but on ISP server. It makes me wonder what differens there are between the buttons, except that I return to the content list on submit. Are there more database queries after a "submit"? (I suspect my ISP have problems with the DB-server...)
(running CMS Made Simple 2.1.2)
Performance differens Submit and Apply
-
calguy1000
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: Performance differens Submit and Apply
The 'apply' button gathers the form data and sends it via ajax, one single request, and there is no redirection, no need to load the admin theme or anything. on the server side in the handling of the submission the code is exactly the same between apply and submit.
The difference is in what has to be read from the database, and processed for display.
On submit the form is submitted via regular multipart-form-data POST which means that the system loads the admin navigation, and does a normal CMSMS request and then the user is redirected back to the main ContentManager page to again load the admin navigation and additionally load content pages and build a content list form. Essentially two full requests with all images and stylesheets and cruft.
So yeah, there is a performance difference (that's one of the reasons we use ajax for the apply button). if it's dramatically slower there could be a number of causes:
a: problematic mysql server
b: proxies and/or other lag in communication between you and your ISP.
c: something weird preventing admin stylesheets and images from being cached (HTML should never be cached on admin requests, but scripts and stylesheets and images prolly can be for most people).
c: somebody let some ether out of the ethernet
The difference is in what has to be read from the database, and processed for display.
On submit the form is submitted via regular multipart-form-data POST which means that the system loads the admin navigation, and does a normal CMSMS request and then the user is redirected back to the main ContentManager page to again load the admin navigation and additionally load content pages and build a content list form. Essentially two full requests with all images and stylesheets and cruft.
So yeah, there is a performance difference (that's one of the reasons we use ajax for the apply button). if it's dramatically slower there could be a number of causes:
a: problematic mysql server
b: proxies and/or other lag in communication between you and your ISP.
c: something weird preventing admin stylesheets and images from being cached (HTML should never be cached on admin requests, but scripts and stylesheets and images prolly can be for most people).
c: somebody let some ether out of the ethernet
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
-
Bigge
Re: Performance differens Submit and Apply
Thanks for your reply.
Now I have a better understanding and can dig for the cause of the problems.
Now I have a better understanding and can dig for the cause of the problems.
