We've been using 4D Client as our Active4D web server for a couple of
years. While we knew we'd take a speed hit, not having some rotten
code bring down the server was a benefit that far outweighed the loss
in speed. 99% of the time with what we do, the server is as fast as
we need it. However, the 1 percent points out what kind of speed hit
we do get.
I wrote a report script that goes through a bunch of records and
tells our Project Managers what is screwed up in the projects they're
managing. A "bunch" roughly being 20 Project Managers with about 20
Projects each, that have an average of about 500 detail records (that
are another level down). The script looks at the latest one (order by
timestamp <) to do some calculations. That's roughly 200,000 records
(probably a high estimate) and the detail records are in groups that
sometimes have to be further reduced. Running it on our development
machine (which has Active4D running on the server) the script took
about 8 seconds to execute from the browser view. I later added a
tick count and it took about 400 ticks. Running it on the 4D Client
as the web server, the same process took about 90 seconds and about
4700 ticks! Roughly 12 times slower.
Just a little food for thought. Still would not go back to the server
as the web server, at least not as long as clients are connecting to
it. This audit report is something I'll run on a weekly basis and not
a link that someone is going to wait 90 seconds to get the answer. If
I need that, we'll go the stored procedure route. Should also point
out that our Active4D crashes are almost non-existent, but
occasionally someone tries a little tweak that finds some rotten code.
Steve Alex
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
