On 19 Dec 2011, at 20:37, Aparajita Fishman wrote:
I could change this to be configurable, so that it would only yield
after N lines of code, which would effectively give more CPU to
Active4D and less to the database engine. So you would probably want
to do this only on the Clients
That sounds like a very useful option (at least in my case).
By the way, after further testing, the framework code turns out to be
only around 30% of the hit (i.e. 0.3 x 0.4 = 12% overall hit). The
rest is either extra code that I've added or some specific bottleneck.
Also, my customer informs me that this site is actually very fast as
rated by Google, so we don't necessarily have a performance problem -
it will now be not so fast but hopefully still reasonable. I'm just
trying to account for the performance price of the new developments.
Another interesting thing that came up in tests today is the
difference in behaviour between 4D and NTK -
- with 4D WS under high loading, the socket error rate is about 40%
but response times on the remaining successful requests is under 5
seconds
- with NTK, using Rob's new function to set the socket backlog queue
length to 128, the error rate drops to zero but response times jump to
25-30 seconds
From my customer's point of view, they prefer the long response times
(albeit potentially with some other managed throttling - e.g. limited
requests with friendly user messages) to socket errors. They
definitely do not want their business customers to see socket errors
as it's a great way to drive them straight to competitor's sites,
never to be seen again.
An alternative to NTK's backlog controller is Apache (that's what they
currently use).
They also would like to look into caching in Apache - there are issues
to be addressed here such as preventing session based content from
arriving at the wrong browser - but the potential benefits are
significant since the data set remains static for several hours
between revisions.
If anybody reading this has tried caching in Apache with dynamic sites
I'd be keen to know how it worked out.
Regards
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://list.aparajitaworld.com/listinfo/active4d-dev
Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
