I agree! FWIW - debugging performance of forked Unix process startup/overhead is a mess - we had one customer who was seeing terrible performance when fork/execing tiny little shell processes that did practically nothing. It was only happening on one of their LPARs. The IBM Support center was involved for a really long time, and I don't know if they ever really figured out what was wrong.
On Fri, Aug 23, 2019 at 8:24 AM Jerry Callen <jcal...@narsil.org> wrote: > According to the "Summary of changes for z/OS UNIX System Services > Planning for Version 2 Release 4 (V2R4)" (see > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxb200/bpxb2soc24.htm), > copy on write for fork() has been removed from z/OS. It will be interesting > to benchmark the performance of fork() between 2.3 and 2.4 on a variety of > processes. > > I wonder why this was done? (Hi, Peter Relson -- hint, hint...) > > -- Jerry > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
