Just FYI, the following 2 parameters are strictly for performance and you'll likely want to evaluate for PROD:
#wrapper.java.additional.9=-XX:NewSize=256m
#wrapper.java.additional.10=-XX:MaxNewSize=256m
However, the following parameter is usually required for the OTM web and app server to startup correctly - as this defines the memory space that the JVM uses to hold objects like classes and methods. (Reference:
-XX:MaxPermSize - CauchoWiki ) If this is undersized, sometimes OTM won't start -- and other times it will simply crash when large workloads are processed.
#wrapper.java.additional.8=-XX:MaxPermSize=384m
The problem with running on Win32 is that your total JVM memory size (MaxPermSize + heap) is limited to somewhere between 1200 and 1400MB, depending on how fragmented your memory is at the time the JVM starts up. As a result, you may have difficulties running any significant volumes on Win32 in PROD, as most OTM installations require a heap size of 1536MB to 2304MB for optimal performance.
Hope this helps.
--Chris