Hello Mehoob,
From: "Mehboob Alam" <[email protected]>
I've done some tests that confirm processes started by 4D's New Process
command are not multi-threaded.
I'm sorry that you had to go through the trouble to create tests and
confirm this. It is public knowledge that the 4D language engine is
single-threaded (cooperatively tasked), and this will not change in the
future.
Don't be sorry. My work was not done to determine *if* this is the case, but
to determine how much it will impact me. "Proof of Concept" is often a good
idea,
If you need to create a large scalable system, you can create multiple "4D
RUNTIME" instances that communicate to a single "4D SERVER" via SQL, and
get the maximum of your multi-core server.
That's what I've been doing, from Day-1. The design is also extremely robust
and resilient, with the ability to scale to "lots of" distributed-process
clients, and to automatically detect hung processes and to reassign them to
another distributed-process client. No surprises here.
Keep in mind, the 4D Server license is priced accordingly, an additional
license per core. You may want to price out your multi-core capable server
license with 4D before you continue architecting your system.
According to 4D, the company, 4D Server v11 is licensed per client (2
standard, with optional expansion) when working in client/server mode, and
by core (2 standard, with optional expansion) when using the unlimited SQL
connection. My design is a combination of client/server and web, with no
need for the unlimited SQL connections.
-Steve Makohin
Oakville, Ontario, Canada
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
