Dashboard performances after developpement

[Stephanevg]

trafficstars

Hi,

I have been developping my dashboard, and after a short while my dev system becomes really really slow.

I am probably using the wrong approach, but this is how I work:

I do some developement (implement some counters, I read some data out from CSV's etc..) and display it.

I do quite some modifications. To do so, I do a:

get-UDDashBoard | stop-UDDashboard

After some developement time, and a few get / stops (I am around Dashboard22) the server starts to be super slow. I stoped the dashboard, and closed the ISE, but the ISE is still using a huge amount of ressources

Is this the wrong way to use UD in a developement mode? Is there a way I can easily free up more resources, or is Get-UdDashboard | stop-UDDashboard supposed to be enough?

I would also love to have the possiblity to set Breakpoints.

Stéphane

[adamdriscoll]

Whoa! No, that seems like a bug in UD. Something isn't being cleaned up correctly. Until I can correct this you might need to stop the ISE here and there to prevent this from happening.

Check out this documentation on how to set breakpoints in Endpoints: https://adamdriscoll.gitbooks.io/powershell-universal-dashboard/content/debugging.html

[Stephanevg]

After a few more tests, I seems I have having the issue "only" when I use a New-UDTable. Ass oon as I remove the UDTable, The performances are back to normal.

[BryanDM]

Stephanevg, What kind of object are you passing to Out-UDTableData? I ran into a similar issue with a Grid. It was happening when I was passing an object from Invoke-Sqlcmd. I was able to get it working by piping it to select-object and selecting all of the columns I wanted.