Debug Performance

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
datacore.glenn
Posts: 30
Joined: Mon Apr 09, 2012 1:45 am

Debug Performance

Post by datacore.glenn »

PowerShell Studio 2017 v5.4.143
Windows 10 Pro, 64-bit

Hello Support,

Not so much a bug as an observation that I share with some other users and an associated request. I created a particular project around a year ago. It's of reasonable size (~12k line Module), has around 70 variables in scope at any point during a breakpoint, of which most are simple types (string, integer) but a handful are XML documents (between 750-2500 lines).

In short, having revisited it this week, it is very noticeable that step-by-step debugging performance has decreased considerably from prior versions - it takes around 5 seconds between F11 key presses for the Variables Panel to update, and the UI to become responsive and allow the next step to be taken. A new project, which makes use of large SQL datasets, is almost impossible to debug in this way, taking 30 seconds or more to update between steps. In both cases the problem can be overcome by closing the Variables Panel and opening it only when needed but it's not ideal and the refresh delay on opening the panel is still present.

If I have read other posts on the subject correctly, the additional overhead coming from saving session state at breakpoints (for improved Primal Sense support) is the root cause, introduced in service build v.5.4.142? If that is so, is there a way to disable this behaviour and thereby revert to the previous level of performance, whilst keeping the variable panel open? If not, could there be in future?

Regards,
Glenn

User avatar
davidc
Posts: 5913
Joined: Thu Aug 18, 2011 4:56 am

Re: Debug Performance

Post by davidc »

At this time, there isn't anything you can do (other than closing the panel). Unfortunately, this has to do with the data collected by the debugger. Note: 143 improves performances over 142 and we are looking at ways to improve this further. In the next service release, we will add a delay before loading the variable data, which should give you enough time to step before trigger an update in the variable panel.
David
SAPIEN Technologies, Inc.

User avatar
davidc
Posts: 5913
Joined: Thu Aug 18, 2011 4:56 am

Re: Debug Performance

Post by davidc »

Depending on what you have in the Watch Panel, that could also add delay.

Alternatively, if you want to monitor certain variables, close the Variables panel and use the Watch Panel with specific expressions.
David
SAPIEN Technologies, Inc.