Hi guys,
every time i edit a page using the my source matrix back end, it always ends up to php timeout. the website loads ok but the slow part is when i go edit the pages and hit the commit button…
The client is really on panic right now. 
is anything we can do with this?
Thanks
[quote]Hi guys,
every time i edit a page using the my source matrix back end, it always ends up to php timeout. the website loads ok but the slow part is when i go edit the pages and hit the commit button…
The client is really on panic right now.
is anything we can do with this?
Thanks[/quote]
Have you checked in php.ini for the line that talks about the maximum time that php can execute a script? If this is a really low number php is going to time out. This normally happens for things like a parse file, but I have never seen it on normal pages in the admin interface.
well at first the parse files are the one that got timed out. so we stopped working some edits on them. now all standard pages are are all behaving very slow abd always causes timeouts..
we checked the php.ini and find out a 30 seconds scripts executing in the server and we tried to put it up and will see what will happen..
[quote]well at first the parse files are the one that got timed out. so we stopped working some edits on them. now all standard pages are are all behaving very slow abd always causes timeouts…
we checked the php.ini and find out a 30 seconds scripts executing in the server and we tried to put it up and will see what will happen…[/quote]
I would caution against increasing the timeout too much and for an extended period, as the waiting processes will begin to stack up in Apache, potentially causing further performance issues.
If you are a Squiz client, please contact Squiz Support so we can track down why this may be occurring.
[quote]I would caution against increasing the timeout too much and for an extended period, as the waiting processes will begin to stack up in Apache, potentially causing further performance issues.
If you are a Squiz client, please contact Squiz Support so we can track down why this may be occurring.[/quote]
Hi Mark
How would you gauge the length the max execution time should be? Also, when you say stack up, would they be waiting for IO or something else?
The maximum execution time specified would be dependent on a number of factors including the website traffic received. Because of this I cannot recommend a value apart from the fact that 30 seconds is not causing any other known issues for other installations.
Generally speaking, the web request received by the server will execute PHP scripts up until the maximum time. As there are multiple requests at any given moment, an increase in the timeout period will increase the amount of pending requests on the server. These processes could be waiting for any number of things, such as results of large DB queries (waiting for Oracle / PostGres) or processing elements in a loop.
[quote]I would caution against increasing the timeout too much and for an extended period, as the waiting processes will begin to stack up in Apache, potentially causing further performance issues.
If you are a Squiz client, please contact Squiz Support so we can track down why this may be occurring.[/quote]
i got a feeling that there were already too many pending process to the DB which causes the load speed problem. if we restart the DB, will the pending processes to it will also be gone?
or does anybody knows some possible causes for this sudden load speed problems?
the weird thing is only the matrix backend has the laodspeed problem and not the live site. if i changed something to the parsefile through backend, the codes from the backend did change but not on the live site. :(
Restarting the DB will have no effect on the processes in Apache, however these will be cleared within 30 seconds anyway. If there are long processes still running on the DB, there should be an SQL query that can be issued to remove these processes without restarting the server. (Sorry I can't remember what this is for PostGres)
[quote]the weird thing is only the matrix backend has the laodspeed problem and not the live site. if i changed something to the parsefile through backend, the codes from the backend did change but not on the live site. :(:([/quote]
Please verify that the backend URL corresponds to the frontend of your site, it seems that you may be editing from a URL other than that of the live site.
Edit: Minor typo
[quote]Restarting the DB will have no effect on the processes in Apache, however these will be cleared within 30 seconds anyway. If there are long processes still running on the DB, there should be an SQL query that can be issued to remove these processes without restarting the server. (Sorry I can't remember what this is for PostGres)
Please verify that the backend URL corresponds to the frontend of your site, it seems that you may be editing from a URL other than that of the live site.
Edit: Minor typo[/quote]
yes the backend url has the same domain of hte live site. even if ill just us the "_edit" code on the las part of the url, it always timeouts whenever i hit the commit button.
does the backend and live site has different DB/ schema?