On Nov 1, 2016, at 5:49 PM, David Adams <[email protected]> wrote: > > I'm not going to answer either of Tony's questions as I don't feel > qualified to say one way or another. I'll admit that I've paid almost no > attention to the preemptive/cooperative subject in upcoming versions of 4D. > Can those of you who have tried it all out and gotten some experience > provide a bit of background? Specifically: What problems does this help > with in your systems. I can easily see why 4D has put a lot of effort into > improving threading in their server code, what I'm not clear on is which > problem(s) or classes of problems this will help with meaningfully that > fall into our hands. I'm not suggesting there aren't problems like this, I > just don't know what they are.
I haven’t tried out 4D’s implementation and am not likely to do so in the near future. However, things I have used multi-threading for: Cocoa apps - cropping/resizing/exporting/importing images (huge performance gain), performing http requests, loading thumbnails to cache, etc. Ruby/Rails apps - processing large numbers of files; performing slow fuzzy search on slices of data; There is a certain satisfaction from converting a lengthy single-core operation to a short one that lights up all cores at 100%. Jim Crate ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
