R
Rob Fitzpatrick
Guest
There are various vintages of Progress profiler viewers, all of which are officially unsupported. But the ABL profiler system handle is supported. What is the value of being able to generate profiling data is there isn't a supported way to visualize and analyze it? Such a tool may have been categorized as "nice to have" in the nineties but today I believe such tooling support is a necessity. Also, the profiling database should use Type II storage and it should be possible to use the application in a client/server configuration without resorting to editing the code. Why client/server? Because on the Windows desktop, with a development license, the user probably only has a Personal database license, thus no access to large file support. A while back I needed to analyze profiling data from an application that generated lots of profiling data (several GB) very quickly. The session load process churned away for hours before failing because the profdb extent filled up. I would rather put the profiling database on a Linux DB server where I can benefit from fast processors, fast disks, and an Enterprise DB license. Then I would load the data server-side and view it client-side. Yes, I can work around this somewhat by adding extents to the DB but that doesn't address all of the issues above.
Continue reading...
Continue reading...