Hi Ed, >We are beginning to transition our servers from Mac to Windows. For those >of you who have made the journey, what have you found to be best practices >for a built c/s app running on Windows Server 2016 Standard? Are there any >gotcha's we should watch out for? Direct roads to smooth sailing?
Running 4D Server under Windows Server is pretty straightforward. I don’t know about specific WS 2016 issues, but in general there are only a few things to set for 4D Server to run best. One thing to make sure is to set it to be optimized as a data server, not a file server. In WS 2008 that setting was in the “Performance Options” control Panel, but may be elsewhere in v2016. >Our initial tests will be on a Virtual Machine. We can transition to bare >metal if the VM's do not meet our performance expectations. Thoughts? In my experience, a VM will perform best with 4D when dedicated resources (disk space and RAM) are allocated for 4D. The ‘smart’ features of VMs which manage application memory and disk priority should be disabled for 4D. Other things to consider: - 4D Server on Windows has been 64 bit for a very long time, so that may be something new for you. You’ll be able to set the 4D Cache much higher. Check out the 4D Tech Notes for details, but basically you can set the 4D Cache to 50% of RAM. - Under v17 you can use Volume Shadow Service to have Windows make an automatic snapshot backup. That’s a good thing, but if you aren’t using v17 you’ll need to make sure you disable the VSS service on Windows Server. It has the potential to cause problems with the 4D database. - You may also need to increase the size of the process stack for new processes you create in 4D. It should be at least 128,000 bytes. Others with more recent experience than mine will hopefully add to or correct this list. HTH, Tom Benedict ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
