I don't know. In some simple tests without any contention from multiple processes, both reading and writing took 0 ms.
I did not know Storage was slow until this thread came up. I did not see that in the documentation, maybe only something you learn about if you go to the conference. Without some published benchmarks, it sounds like 4D folklore at this point. What seems *really* slow to me is CALL FORM. I'm seeing about 100ms between CALL FORM and the time the method starts executing in the form process (not called from the same process as the form window). John DeSoi, Ph.D. > On Aug 27, 2018, at 10:04 AM, Keith Culotta via 4D_Tech > <[email protected]> wrote: > > Does the speed penalty apply to reading values from Storage, or just to > writing values to Storage? > > > >> On Aug 26, 2018, at 8:57 AM, John DeSoi via 4D_Tech <[email protected]> >> wrote: >> >> Storage is the best option for interprocess communications if you want to >> use preemptive processes. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
