If you look in Service Center’s Administration tab, you will see a setting for “Running Mode”. On Personal Environments, this is read-only. The basic mechanics of Production and Development modes are documented.

The “Running Mode” setting

However, what is not documented is “why should I not just turn ‘Development Mode’ on for my Production environment?” After all, it sounds potentially useful, right?

The answer is “performance”. Using Development mode, or enabling debugging on an eSpace in Production, adds debugging symbols to the compiled code. This greatly increasing its size (and therefore how much RAM it uses) as well as significantly slowing down its execution speed. You won’t notice the difference in a development or QA environment, but load hundreds or thousands or users against it and there will be a difference for sure.

So… while there is a time and a place to turn on debug for an eSpace in Production, or Development mode for the entire Production environment, please remember to keep it off except for those rare moments where you absolutely must debug a live Production environment.

J.Ja