Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
On 05/11/2014 10:50 AM, Martin Schreiber wrote: Have you ever concurrentely read strings from different threads? I do this all the time. -Michael -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
On 05/11/2014 08:06 AM, Martin Schreiber wrote: Hi, Because of the big overhead by locked refcount operations and memory barriers long strings and dynamic arrays are not thread safe, even reading needs serializing if the data will be accessed from several threads. In exactly what environment is this true ? Of course any language-introduced operation needs to be thread-save ! If library functions are not thread-save this needs decent documentation. Composed Types (records, Objects, problem: complex and int64 on a 32 Bit CU) need to be documented as not being allowed to be considered a being handled in an atomic way, but it should be save to use Strings (as any not obviously composed language objects) in any thread without restriction. OTOH, e.g saying TList is not thread save is not clear enough, It should be stated that using multiple instances of TList in multiple threads is save as long as the same instance is not used in multiple threads. OTOH TThreadList is supposed to be thread save even in this use. -Michael -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
On Monday 12 May 2014 09:37:25 Michael Schnell wrote: On 05/11/2014 08:06 AM, Martin Schreiber wrote: Hi, Because of the big overhead by locked refcount operations and memory barriers long strings and dynamic arrays are not thread safe, even reading needs serializing if the data will be accessed from several threads. In exactly what environment is this true ? The overhead? Every operation which inc/dec's ref count, for example stringvar:= stringexpression; procedurecal(stringparameter); ... AFAIK memory barriers are extremely evil. Martin -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
On 05/12/2014 10:40 AM, Martin Schreiber wrote: AFAIK memory barriers are extremely evil. Of course with modern CPUs this is correct. Anyway, not allowing normal seemingly innocent language types for ubiquitous use asks for an infinite count of problems. -Michael -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
On Monday 12 May 2014 10:57:27 Michael Schnell wrote: On 05/12/2014 10:40 AM, Martin Schreiber wrote: AFAIK memory barriers are extremely evil. Of course with modern CPUs this is correct. Anyway, not allowing normal seemingly innocent language types for ubiquitous use asks for an infinite count of problems. Managed types apparently are not innocent. ;-) Martin -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
On 05/12/2014 11:02 AM, Martin Schreiber wrote: Managed types apparently are not innocent. ;-) That is obviously for language developers. But to the language users thy seem to innocent ;-) -Michael -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
The overhead? Every operation which inc/dec's ref count, for example That's why me recommend both types - You may implement unsafe types first and safe ones later. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
Opinions? Two options with distinguishable syntax. var1: int; threasafe var1: int; or var1: int threadsafe; -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
On Sunday 11 May 2014 10:30:13 Ivanko B wrote: Opinions? Two options with distinguishable syntax. var1: int; threasafe var1: int; or var1: int threadsafe; Have you ever concurrentely read strings from different threads? Martin -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
Have you ever concurrentely read strings from different threads? == With memory access hooks etc ? No, but there may be such need - it's even obvious from Your question. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] MSElang, long strings and dynamic arrays are not thread safe
I looks like DB issues about concurrent accessing shared data. There're a few 100% working access disciplines for that - SHARE, SHARE READ, SHARE EXCLUSIVE etc. For instance, they may introduce read waiting for another's change to commit. How about implemention those with thread-safe variables ? -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
