With Java and shared classes, it keeps a copy of the compiled classes in a data space. You can now "save" the latest image to disk, and reload that next time you run. If you save it every day, you will be able to restore the latest and greatest optimised version. Without the shared classes, the first use after IPL is slow, the second is much faster. See "Some of the mysteries of Java shared classes" <https://colinpaice.blog/2021/05/24/some-of-the-mysteries-of-java-shared-classes/>
On Fri, 22 Oct 2021 at 08:52, Andrew Rowley <and...@blackhillsoftware.com> wrote: > On 22/10/2021 2:46 am, A T & T Management wrote: > > Java, it has to be translated each time it run, provided you know > the language and it's been debugged. Schools may teach it but they too > want to make money and look good because they can say it's modern and that > is what they push. Any CEO or executive who doesn't look at the total cost > is doomed to fail. > Don't write off Java too quickly. I previously posted about Software > Drag Racing, which was a competition to test the speed of different > languages. > > In the initial test on z/OS, Java was over 3 1/2 times faster than C++. > With some tweaking, C++ ran as fast as Java, but not significantly faster. > > The results are written up here: > > https://www.blackhillsoftware.com/news/2021/08/10/java-vs-c-drag-racing-on-z-os/ > > If you have a zIIP and your general purpose CPs are not full speed, Java > might be the fastest language on your system by a big margin... and it > doesn't count against general purpose CP usage. > > Java will compile to machine code where it makes a difference to > performance. Just in Time compilation has some performance advantages: > - it can optimize for the exact hardware > - it can leave out infrequently used code paths and compile them later > if they are actually required, making the machine code smaller and more > efficient > - it can monitor the code execution and recompile the hottest parts with > extra optimizations > > IBM also talks a lot about RNI and processor cache... it turns out > garbage collection is good for cache efficiency too. It moves all the > active data into a smaller chunk of memory, which makes better use of > processor cache and is good for your RNI. > > If you have well defined, well understood programs that are big CPU > users, it certainly could be worth rewriting them in Java. > > (Knowing the language and debugging programs applies to any language... > and I'm not denying you can write large programs and inefficient code in > Java as much as in any other language.) > > Andrew Rowley > Black Hill Software > > ---------------------------------------------------------------------- > 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
