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.
Regards, Aparajita www.aparajitaworld.com "If you dare to fail, you are bound to succeed." - Sri Chinmoy | www.srichinmoy.org _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
