...
Analyze Data In Debug Log
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
115-05-04 14:02:18.684 [debug3]ELAPSED TIME FOR SCHEDULER REQUEST: 0.172s
115-05-04 14:02:18.703 [debug3]MODIFY DATETIME ATTRIBUTES:
115-05-04 14:02:18.725 [debug3]ELAPSED TIME FOR MODIFY DATETIME ATTRIBUTES: 0.022s
115-05-04 14:02:18.743 [debug3]ELAPSED TIME FOR SCHEDULER TREE REQUEST: 0.521s
115-05-04 14:02:18.762 [debug3]START MODIFY RESPONSE left_frame
115-05-04 14:02:18.782 [debug3]ELAPSED TIME FOR MODIFY RESPONSE: 0.02s
115-05-04 14:02:18.801 [debug3]WRITE HTML
115-05-04 14:02:18.820 [debug3]START TRANSFORM RESPONSE frameset
115-05-04 14:02:18.937 [debug3]ELAPSED TIME FOR TRANSFORM RESPONSE frameset: 0.117s
115-05-04 14:02:18.957 [debug3]ELAPSED TIME FOR WRITE HTML: 0.156s
115-05-04 14:02:18.975 [debug1]ELAPSED TIME FOR UPDATE left_frame: 0.79s
115-05-04 14:02:18.995 [debug3]HTTP REQUEST STATUS onComplete 200
115-05-04 14:02:23.286 [debug2]EXEC update_periodically_checkbox__onclick("[object HTMLInputElement]") in top_frame
115-05-04 14:02:23.305 [debug4]DELAYED EXEC (0.001s): parent.left_frame.repeat_update( parent._scheduler._update_periodically, parent._scheduler._update_periodically ); called by update_periodically_checkbox__onclick in top_frame
115-05-04 14:02:23.324 [debug2]ELAPSED TIME FOR EXEC update_periodically_checkbox__onclick("[object HTMLInputElement]") in top_frame: 0.038s |
From the JOC debug message one can see the time taken by JobScheduler engine to prepare the information packet and also time taken to update JOC GUI etc. By analyzing time taken by different operation request --> response --> rendering you can find out what is causing JOC performance degradation.
JOC Performance improvement
- Organizing JobScheduler objects e.g. job, job chain under directories and sub directories.
- In case of higher number of JobScheduler objects JOC's tree view render faster compare to list view.
- Using JobScheduler with Jetty Web server rather then JobScheduler's inbuilt Web Server also has visible performance improvement.
- By increasing auto refresh / Update time to 30-45 seconds also reduce load on the JobScheduler engine.