you got me on that one, gil. :) trying to exploit the ambiguity of a Sunday. guilty.
i got a side gig to figure out some performance problems, and it ain't on linux, but on a real machine. and nothing is good on tv at the moment. as Lizette pointed out, elapsed time is one thing independent on cpu. and vince pointed out my lack of knowledge. on unix (linux) cpu can go over 100%. but for some reason I thought that no matter what on mvs, 1 cpu second (unless multithreaded) equaled 1 second at least wall clock time, no matter the cpu configuration. I could have perhaps asked this a better and more mainframe way: In the JES log from a batch job, will I ever see an elapsed time less than the CPU time? /Lindy -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: sunnuntai 9. huhtikuuta 2017 19.03 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CPU Timerons/Seconds vs Wall-clock Time On Sun, 9 Apr 2017 15:48:12 +0000, Lindy Mayfield wrote: >This may or may not be the dumbest question I've asked this week, but I've >been working with Linux a lot lately so that's my excuse. > (It's only Sunday.) (On what day does Finland(?) start the week?) >For example, if an MVS job ran and consumed 10 CPU seconds (SMF 30 I think), >can I assume that it at least took 10 seconds of elapsed time to run? > How do multiple CPUs count? Might it be 10 seconds/number of CPUs active? -- gil ---------------------------------------------------------------------- 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
