On 24 Jan 2008, at 03:54, Aparajita Fishman wrote:
I would *strongly* recommend against using Client as the web server
in a high load environment, for two reasons:
Ouch.
This is no longer a practical option. There are 3 sites all using the
same datafile (different data sets) running on 4D Client. Also, one
of the 4D clients is a dedicated admin server accepting very large
daily uploads of product and stock info (we structured it this way so
that the product uploads would'nt kill the performance on the primary
commercial web server, even though it had to be dumped into the same
datafile) The admin client also facilitiates the 2-hourly downloads
of orders.
1. You are being severely penalized for the cost of transferring
database data over the network from Server to Client.
That would seem to be the least of our problems on the face of it.
Having done lots of analysis, the query time is one of the smaller
components of the response time and seems scaleable and acceptable.
The main problem at the moment is the dropped connections.
2. The web server in Client is not as robust as the one on Server.
I wish that when 4D launched web server on client it had come with
such a health warning, however, I get exactly the same behavior on 4D
standalone (haven't tried 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
Absolutely, this exactly how I've got it structured at the moment.
Thanks for the response !
Best Regards
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
