Hey Tim, On Thu, Oct 10, 2019 at 10:43 AM Tim Nevels via 4D_Tech < [email protected]> wrote:
> So what you are saying is that if you are deploying 4D Server in a VM > there is not need to try and use preemptive mode. You get no benefit from > doing that. It’s a waste of time? That's what I got. Thomas showed a demo app he wrote deployed on AWS or the like and using a lot of cores (32?). But it did not improve the overall processing time. The reason being, as I understand it, the whole benefit of preemptive mode is to allow 4D to assign a process to a core. But in the case of a VM the actual, physical cores are managed by the VM. It really couldn't be otherwise and support all the cool stuff that makes the VM attractive. I don't know that makes preemptive a waste of time but it does mean you need to think about where your db will be running to decide if it's worth the effort to implement it. On the other hand this means that in a VM environment CALL WORKER is pretty much as useful and a lot less hassle. It would be interesting to know if preemptive is something that can be called for a local process on a client machine. Now _that_ would be pretty handy. Ask JPR when you chat with him. -- Kirk Brooks San Francisco, CA ======================= What can be said, can be said clearly, and what you can’t say, you should shut up about *Wittgenstein and the Computer * ********************************************************************** 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] **********************************************************************
