Hi Lutz, Jeffrey, Thanks for your answers.
So it is about using 64-bit, and writing preemptive-safe methods I see a lot of 4D commands turning into preemptive-safe commands, so that's good Now for me probably work has to be done, but I am confused what is needed. 1. We don't use 4D tables, we use 4D for OCI and variables and arrays 2. We don't use 4D server, we use 4D Volume desktop 3. We start 1 or more processes (new process) in which we show a dialog with data (the variables and arrays) 4. We use a whole lot more in 4D, but nothing to do with 4D datafiles / 4D data query 4D queries etc. So, does 4D automagically use more cores in 4D 64-bit or what? When I follow all pre-emptive advise in the docs or from the iNUG, do I have a multi-core application? Gr, Piotr Compiled 64-bit Volume Desktop can use more than one core, depending upon how you write your code. 64-bit 4D is required, as is being compiled, in the current implementation. You need to write preemptive-safe methods and your methods need to be marked as preemptive in the method properties. > On Jan 30, 2019, at 4:48 AM, Pat Bensky via 4D_Tech > <[email protected]<mailto:[email protected]>> wrote: > > Piotr > I believe the "bitness" has more to do with how it uses RAM than cores. > Pat > > On Wed, 30 Jan 2019 at 09:13, Piotr Chabot Stadhouders via 4D_Tech < > [email protected]<mailto:[email protected]>> wrote: > >> Hi all, >> >> First of all, I must say I am no hardware expert, so maybe this is a >> stupid question. >> >> It seems that 4D 32-bit Volume desktop only uses 1 core. >> But does 4D 64-bit Volume desktop use all available cores? >> >> Gr, >> Piotr ********************************************************************** 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] **********************************************************************
