How can we help you today? How can we help you today?
jlb0001

Activity overview

Latest activity by jlb0001

James, I'm most impressed with the tone and attitude of your response. You could have said that you just didn't have it in the plans and that the features requested here were simply bad ideas. But you didn't, and I applaud that. A few points I would respond with: (1) RE: ability to attach the profiler to a running process to "instrument" the application ... requires us to [re]start the application so that we can register our handlers That's fine with me. I would add that perhaps there should be a way to pre-register the handlers and simply puy them in "no-op or sleep mode". While they'd get called, they would return immediately while in this mode. The advantage of this is to reduce overhead such that it could be run on a production server and activated once a problem is detected or direct observation is otherwise required. Of course one wouldn't want this on all the time, but that is the perogative of the developer/admin (i.e. caveat emptor). I further encourage you to explore ways to "attach" to running processes without restarting the process. Maybe this means requiring that applications instrument themselves or even pre-register the hooks that are then delegated to ANTS if they want that feature available? (2) RE: remote profiling capability (e.g., VS remote debugging tools) I do not think this will make it into 4.0 but it is certainly on our list for future versions. Would this be less useful without the attach to process funcationality? I hope this is on the short list. And yes, it would still be useful if the ability to attach to a process is not available. In our case, the test setup is not feasible on a workstation due to the number of dependencies and complexity of the setup. So, it'd be very useful to be able to profile a remote system by simply installing a proxy profiler service on the target server. (4) the perogative of "power users" vs support An additional point I would like to elaborate on is the perogative of the developer. A tool may offer options which can be used in really bad ways -- Visual Studio is a perfect example. From a support perspective, Red-Gate has an incentive to reduce those "power user" options to prevent having to deal with users who don't know better. Taking those potential options out of the GUI is one way to reduce their use by novices that take it the wrong direction. If it means the choice of not having a feature or not having it in the GUI, then that's a choice I'm OK with that if it means we get more power user options. Over-simplification has been ANTS biggest flaw in the past, and we've not been able to use ANTS for this reason. As much as simplicity rocks, the art of debugging and profiling require tools that are up to the task. This may mean sacrificing a bit of simplicity for the sake of power options. After all, profiling itself is a power user task. So, instead of worry what inexperienced users might do wrong with the tool, I encourage Red-Gate to take some risks and add more power user features. Put warning signs on these options. Don't offer the same level of support for those options. Charge more for those option to segment your market and to pay for that extra support staff. But, whatever you do, don't skimp on the power user options! Again, thanks James for the positive attitude and willingness to expand the feature set to meet customer needs. -Jonathan / comments
James, I'm most impressed with the tone and attitude of your response. You could have said that you just didn't have it in the plans and that the features requested here were simply bad ideas. Bu...
0 votes