On the load test, the stress testing package reports about 84%
'Socket Errors'. Can anyone throw any more light on this with
respect to how 4D behaves, namely:
- what exactly is a 'socket error', is it an OS level problem,
nothing to do with 4D? or a 4D overload ?
A socket error would be a problem with the TCP/IP connection routines
used by the 4D web server.
- are there any settings in 4D Prefs (or OS prefs) which can
influence this aspect of performance ? (e.g. Max web processes,
Number of requests per connection etc)
That depends on what exactly the socket errors are. Unfortunately your
tool is not giving you much useful information.
Environment:
4D 2004.5 Windows (Standalone & Client Server [Client as web server])
I would *strongly* recommend against using Client as the web server in
a high load environment, for two reasons:
1. You are being severely penalized for the cost of transferring
database data over the network from Server to Client.
2. The web server in Client is not as robust as the one on Server.
You should put static content in the folder indicated as the web root
within 4D (what Active4D calls web_decoy). I now structure my sites
like this:
web
<Active4D stuff>
web_static (formerly web_decoy)
css
images
js
All urls to static content begin with /css, /images, or /js
respectively. 4D finds the static content and serves it directly,
using the 4D web server cache if you want. Anything not found in
web_static is passed to On Web Connection and thus to Active4D.
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/
