Administering Applications in Production
Posted by nicholsr on November 5th, 2009. Other posts by nicholsr
Recently we have had a number of queries about poor performance of sMash applications which have turned out to be caused by starting the applications from App Builder.
App Builder is intended as a development tool and as such it always starts applications in debug mode. This has a fairly dramatic effect on the performance of applications, particularly those that use PHP.
To start an application for performance or load testing you should be sure to use the CLI or the administration console instead of using App Builder.
Tagged as administration, appbuilder, cli, debug, mode, performance, php, production, test | Filed in Development
2 Comments » 
(0 votes, average: 0.00 out of 5, rated)
Loading ...2 Responses to “Administering Applications in Production”
Leave a Reply
Event Calendar
Highest Rated
- A tangled web of names: ProjectZero, projectzero.org, WebSphere sMash, IMPACT and IBM
(5.00 out of 5) - Sugar on sMash on EC2 (5.00 out of 5)
- Introducing the… PHP/Groovy Bridge (5.00 out of 5)
- Create a handler to avoid page includes repetition (5.00 out of 5)
- Drupal on Java (5.00 out of 5)
- A tangled web of names: ProjectZero, projectzero.org, WebSphere sMash, IMPACT and IBM
December 27th, 2009 at 10:48 am
Cool. I’m looking for a way to make it run as a Windows service. There is Autoexnt – part of windows resource kit toolbox. It runs a bat file when the service starts, after that the service stops again. But not a sollution for restarting zero applications via one or multiple windows services. Any ideas?
January 4th, 2010 at 9:32 am
There is a discussion on this on the forum: http://www.projectzero.org/forum/viewtopic.php?f=6&t=1597&p=6940&hilit=windows+service#p6940
I will respond there.