Which technical reports datapoint measures the performance of a controller’s script execution if network factors and Web Adaptor processing is…

Processing time is the specific metric that measures the duration required for a server-side component, such as a controller, to execute a script or complete a task. This measurement deliberately excludes external factors like network latency (the time for data to travel over the network) and the overhead from intermediary components like a Web Adaptor. It isolates the performance of the core application logic, which directly matches the requirement of the question to ignore network and Web Adaptor processing.

1. Esri ArcGIS Enterprise Documentation: In performance monitoring for systems using a Web Adaptor

logs distinguish between total request time and the time spent within the server. The server-side execution time is the metric that isolates the service's performance. For example

in ArcGIS Server logs

the time property represents the total duration

while the server property can be used to understand the time spent on the server machine itself

isolating it from network and client-side factors. (Reference: ArcGIS Enterprise Documentation

"Work with server logs

" Log codes section).

2. University Courseware (MIT OpenCourseWare): In performance engineering

end-to-end latency (or response time) is broken down into its constituent parts

including transmission time

propagation delay

and server processing time. "Processing time" is defined as the time the server spends handling the request

distinct from network delays. (Reference: MIT OpenCourseWare

6.824 Distributed Systems

Spring 2020

Lecture 2: RPC and Threads

Section on Performance/Latency).

3. Jain

R. (1991). The Art of Computer Systems Performance Analysis: Techniques for Experimental Design

Measurement

Simulation

and Modeling. John Wiley & Sons. Chapter 3

"Commonly Used Performance Metrics

" defines Response Time as the interval between a user's request and the system's response. It further clarifies that this can be broken down into components

with the time spent at the server CPU being the core "processing time

" distinct from network or I/O delays. (See pages 35-37).