Hi Brad,

I see something similar since I've upgraded 4D-Server to V16 and NTK/A4D
to the newest version.

Before the server could run für month without any issue. After the
upgrade the server slows down within 1-2 days up the point, where each
request can take 10 seconds or even more. According to the 4D admin
panel there are cpu or network intensive tasks running. Server is almost
idle, tons af free memory for 4D. Nothing suspicious in Windows
performance monitor. Rebooting 4D and the slow-down is gone -  for the
next couple of hours, then it slowly reappears.

I realized the slowdown in a JSON API. First I thought it is something
within my A4D code, so I've calculated the time my A4D code needs to
run. But I found the slowdown happens while receiving the request. Once
A4D starts executing the code, everything runs fast, including sending
the response.

I've asked Rob from the pluggers, whether he had heard about slowdows
with the new version of NTK but he wasn't aware of any problems.

In a period, where I wasn't able to restart 4D server periodically,
slowdown got so extreme, that 4D clients were unable to login due to
timeouts. In that state the only way to restart the 4D server was with a
force quit. That convinced me, that the culprit is within 4D V16 and not
NTK or A4D and I should wait for 4D 16.1 and until then restart 4D
Server periodically. That is why I never reported the problem here.

As you have a similar problem but with 4D15.4 makes me wondering,
whether I'm wrong and the lastest versions of NTK and A4D might at least
contribute to the problem.

Hope you find the answer and share it with me.

Greetings

Peter Gutbrod 
_______________________________________________
Active4D-dev mailing list
[email protected]
http://list.aparajitaworld.com/listinfo/active4d-dev
Archives: http://active4d-nabble.aparajitaworld.com/

Reply via email to