Claire, In general, this is correct. The mode is intended for DEVELOPMENT environments.
The tradeoff is serializing some interactive use cases for better memory management and making the developers not conflict so it can impact performance on a production system. On dev, there are few users so really no impact. Doug From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Sanford, Claire Sent: Wednesday, April 17, 2013 11:15 AM To: [email protected] Subject: Re: Multiple Developers on Single Server ** Clarifying... a production system should NOT have that box checked and a development system SHOULD... From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mueller, Doug Sent: Wednesday, April 17, 2013 1:01 PM To: [email protected] Subject: Re: Multiple Developers on Single Server ** Brad (a guess from your email name but if not, apologies), The most important setting for this environment is "Developer Cache Mode". This mode was added specifically to assist this type of environment. We recommend it be set on any system that is a development system where you have more than one developer. What it does is change the way that the AR System server caches definitions it is working on and how it reacts when there is a change to a definition. Some of your slowdowns and freezing can be directly attributed to the model that we have that is designed to allow change in production and production to continue without disruption. The problem is that in development you drive the system a bit crazy with constant copying of the data dictionary cache and maybe having three or more copies of it and possibly having memory blowouts. If you do not have this mode set - see the documentation for the Developer Cache Mode setting that you set in the ar.conf/ar.cfg file - set it and see if this helps. You will need to restart the AR System server after you change this setting. Most environments see the challenges and conflicts of multiple developers significantly reduce (I can never say disappear but significantly reduce is accurate) when going from not having this set to having it set. I hope this helps, Doug Mueller From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of BradRemedy Sent: Thursday, April 11, 2013 11:35 AM To: [email protected]<mailto:[email protected]> Subject: Multiple Developers on Single Server ** Hay Guys Hope everyone is well. Apologies if this has been discussed before and if so would appreciate a point in the right direction to find the information I am looking for. Basically, I wanted to know how you guys handle multiple remedy developers on a single development server. We have 4 developers that are constantly working on the system with object reservation activated. However, we do find that the system is performing slow during the day and at times, freezes and has to have the remedy services restarted. We are thinking of basically giving each developer now their own development area all tied to a central DB to see if that will eliminate the problem. How do you guys handle it? Any ideas or suggestions on how multiple developers on a single remedy application server (DB is on it's own separate server) Any advice would be appreciated. Keep well Cheers _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
