I monitor CPU usage. I have a WEB/SQL that has a lot of components. 70 remote users. 200 tablets.
SOMETHING is running for 1-2 minutes with really heavy CPU.
I get the log message below, but if I could find what Grid or UX is the source, I can find/fix the CPU punishment.
It is not (yet) hurting the users and it is relatively rare.
HOW CAN I DETECT WHAT COMPONENT IS BURNING CPU TIME? Jiving it with the Access.Log is inconclusive.
SQL time is low, but Alpha Server time pins the meter for about 2 minutes.
This it my XBasic.Txt from the Server (Current AppServer release as of today.)
=================================================================
Thu Feb 09 11:14:48 2017
Thread priority reduced.
Thread was busy 95% of the last 20 seconds.
Raw Data: 326522180251717,89934576,326522305631490,91837787,2006076,1903211,20047877,19094522
The script causing this behavior is using a lot of CPU time.
You may want to review the page to make sure you have optimized any XBasic scripting.
Long running and processor intensive scripts tend to tie up available threads and adversely affect the perceived performance for multiple users.
Execution Stack:
0#1 evaluate_shared_private(
0#37 OOhttpdServerClientMIME(ptemp,"AppServerMain")
0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
0#180 x_out = a5_ajax_dialog2(tmpl)
==========================================================
Thu Feb 09 11:15:08 2017
Thread priority restored to normal after being lowered for 20 seconds due to heavy usage.
Execution Stack:
0#1 evaluate_shared_private(
0#37 OOhttpdServerClientMIME(ptemp,"AppServerMain")
0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
0#180 x_out = a5_ajax_dialog2(tmpl)
==========================================================
SOMETHING is running for 1-2 minutes with really heavy CPU.
I get the log message below, but if I could find what Grid or UX is the source, I can find/fix the CPU punishment.
It is not (yet) hurting the users and it is relatively rare.
HOW CAN I DETECT WHAT COMPONENT IS BURNING CPU TIME? Jiving it with the Access.Log is inconclusive.
SQL time is low, but Alpha Server time pins the meter for about 2 minutes.
This it my XBasic.Txt from the Server (Current AppServer release as of today.)
=================================================================
Thu Feb 09 11:14:48 2017
Thread priority reduced.
Thread was busy 95% of the last 20 seconds.
Raw Data: 326522180251717,89934576,326522305631490,91837787,2006076,1903211,20047877,19094522
The script causing this behavior is using a lot of CPU time.
You may want to review the page to make sure you have optimized any XBasic scripting.
Long running and processor intensive scripts tend to tie up available threads and adversely affect the perceived performance for multiple users.
Execution Stack:
0#1 evaluate_shared_private(
0#37 OOhttpdServerClientMIME(ptemp,"AppServerMain")
0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
0#180 x_out = a5_ajax_dialog2(tmpl)
==========================================================
Thu Feb 09 11:15:08 2017
Thread priority restored to normal after being lowered for 20 seconds due to heavy usage.
Execution Stack:
0#1 evaluate_shared_private(
0#37 OOhttpdServerClientMIME(ptemp,"AppServerMain")
0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
0#180 x_out = a5_ajax_dialog2(tmpl)
==========================================================
Comment