Hello Aparajita and list,
From: "Aparajita Fishman" <[email protected]>
So if we create a scenario in which 10 concurrent web users, each
executing a processor-intensive task, can max out a single core for 5
seconds (they experience a 5 seconds response time), then that means 20
users executing the same task concurrently will take about 10 seconds to
complete it (10 seconds response time, about double). This is due to
4D's non-multi-threaded code, and not to the 4D database, Active4D, or
other factors.
The web CPU load is not as high as you think. Active4D can typically
serve about 4 requests per second, and 25% of that time is spent by the
database engine.
Thank you for your quick response.
Granted, Active4D is respectably zippy, but I am thinking of a scenario in
which the user submits a page, Active4D does its work quickly, but then 4D
code is called upon to carry out some computation-intensive work. The
machine on which that 4D code is executing, likely 4D Remote talking to the
4D server, will execute all such code, from all web users, on one CPU core.
Correct?
Again, I highlight that I am *planning* for web development using Active4D
for 4D v11 (to come in the future), and I have not yet done any Active4D
development.
-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/
