On 6 Nov 2014, at 00:16, Peter Schumacher <pl...@4d-consulting.com> wrote:
> 100 is far too low. Set them to 200 or more By the way. When I looked into this a few years ago, the reason I concluded that 4D’s web processes never got up to a significant amount under high loading was that the requests were being rejected at the socket layer before they had a chance to kick off any new processes. i.e. 4D wasn’t able to generate new processes fast enough to absorb the socket backlog in the TCP layer. NTK has a feature that allows you to “tune” this. You can increase the size of the socket backlog queue and that lets 4D absorb a slightly higher load before the queue saturates. The last few days I’ve been working with v14, it feels completely different. There are few or no socket layer rejections which allows the web server (“On Web Connection”) to absorb a much higher load. It’s basically feels like having Apache in front of the old web server. I think this one looks very promising if they can get it stable. Maybe that accounts for your much higher process count - I was working with v12 before, not v13 which is the version they itroduced the new web engine. Peter _______________________________________________ Active4D-dev mailing list Active4D-dev@aparajitaworld.com http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
