Document Zowe and zD&T optimization

[Joe-Winchester]

Is your request for enhancement related to a problem? Please describe.

Zowe is often run on zD&T images. There are tuning options available for this scenario.

Describe the solution you'd like

Document zD&T optimization to get Zowe up and running
refernce:
https://zeeohhsss.wordpress.com/2020/04/23/turbo-java-in-adcd/
https://www.linkedin.com/pulse/running-zowe-zdt-michael-erichsen/?trackingId=DlVV0%2BpIRjWir6fKczG1Wg%3D%3D

[Joe-Winchester]

Also reference the post https://community.openmainframeproject.org/t/configuring-instance-certificates-on-zd-t/5859

[Joe-Winchester]

Doing some experiments I found that the parms

 -Xlp:objectheap:pagesize=1m,warn,pageable -Xlp:codecache:pagesize=1m,pageable \

have the biggest difference.

[plavjanik]

This information is very useful. Is there a way how Zowe configuration scripts can recognize that run on zD&T and use these options automatically?

[Joe-Winchester]

@plavjanik - yes this is possible. I'll get some more measurements and perhaps present it on next week's Arch call to get input. Currently the parms have to be added manually to the start.sh scripts for the various Java runtimes (APIML and Explorer API servers) which means they're not part of the instance.env file (so get overwritten release to release). There may be other variable args that a system programmer would want to set, so perhaps there could be a generic way for a Zowe instance directory to append to the startup args of the different servers based on local tuning.

[plavjanik]

Another useful post - https://emuframe.com/index.php/eng/blog-en/130-z-osmf-2-4-autostart-during-ipl. This and the suggestions from the above link are in the ADCD May 2020 images and z/OSMF starts significantly faster and REST APIs are usable.