Hi Mihael,

Years ago when this feature came out, I was told not to use THREAD(*CONCURRENT) unless I needed it because it adds overhead. I don't remember all of the specifics, but I think it does stuff like create mutexes to make variables thread safe, duplicate all of the static variables to ensure each thread has their own copy, and other stuff.

If you need to write a multi-threaded application, by all means, use it.,

But, if you don't need multiple, concurrent, thread access to your application, don't use this option, it will only slow things down.


On 3/12/19 2:30 PM, Mihael Schmidt wrote:

I was wondering if there is any significant overhead by (or reason against) compiling all RPG programs and service programs with THREAD(*CONCURRENT)?

Usually I only have the constellation that only one thread per job is created. Though when using frameworks like ILEastic multiple threads per job are used. Then every program/service program in the call chain should support multithreading.

I am grateful for every info or opinion.

Best regards


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].