T
tim
Guest
Thanks, that's helpful to know. I could imagine solving this in a couple different ways: 1) Allow specifying that the profiling data be collected across multiple requests but generate a single .prof file -- this data would then be per ABL Session and the agent could be configured to write the data after N requests or when a session is shutdown. 2) Post-process the .prof files and merge them into a single .prof file. The down-side of the first approach is that you can't control which ABL Session will handle which requests (unless you bind the session to a given client). ABL Sessions are chosen based on a most recently used basis, which directs all requests to the same ABL Session on an unloaded (single driver) system, but as soon as its loaded with multiple clients, the request distribution will be somewhat random -- some .prof files might hold lots of request data while others might hold very little. If the post-process was fast and accurate, I think that'd be the way I'd approach it.
Continue reading...
Continue reading...