Hi I seem to have got to the bottom of this. The issue is with v13’s new “Automatic Session Management” property. With this switched on, performance is amazingly silky smooth and stable (compared with v12). With “Automatic Session Management” off, it is jerky and unstable.
In particular, 2 adverse conditions prevail when this feature is switched off: [1] - under moderate loads, every 4th or 5th request “locks up” [2] - if the “Reuse Temporary Contexts (in remote mode)” feature is active and traffic dwindles to the point that some web processes expire due to timeout, the web server will crash when it next receives a request Just so happens that this exactly corresponds to a typical Active4D configuration (since we’ve had automatic session management since the dinosaurs walked the earth). In upgraded databases, the feature is off by default. In v14 native ones, it’s on by default which explains why upgraded ones exhibit the acute condition. In particular: **** Upgraded Structure Defaults ***** Auto Session Man: Off Web Process Timeout: 5 minutes - 1 hour **** v14 New Structure Defaults ***** Auto Session Man: On Web Process Timeout: 8 hours Hopefully this can get addressed before 14.3 is out. I’ll report it on the beta forum. Peter _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
