× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. March 2019

Re: Impact of control option thread(*concurrent)

On 2019-03-12 9:21 PM, Scott Klement wrote:
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.


It's THREAD(*SERIALIZE) that creates mutexes.

THREAD(*CONCURRENT) just gives you separate static storage for each thread. Mutexes are only involved if you code the SERIALIZE keyword on a particular procedure.

I don't know how much performance overhead there is for having separate static storage for each thread, but I assume it would only affect the time for thread-creation.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.