Dynamic Program Analysis - Possible to clear the list
Is it possible to clear the list of DPA results?
I'm trying to exclude system start up queries from the list of database problems, so I'd like to clear the list once it's warmed up.
Please sign in to leave a comment.
Hi!
It is not possible for now, but I've created a feature request. Feel free to upvote!
Hi Jpfortier!
Could you please also describe your case in detail? Is there any method for system start up? For example
Program.StartUpor component container initialization method. If yes it can be suppressed by SuppressMessageAttribute and all the DPA issues disappear at that specific stage.You can answer here or in the comments of mentioned YT issue.
Thank you in advance!
I want to clear them as well, as you can see below I've got 75,000 DB items, clearing them 30 at a time isn't feasible.
Starting debug again doesn't seem to clear them, just more accumulate. This makes it hard to use this tool to diagnose problem as I am not sure which are from the branch I'm on and from which scenario I ran.
Are you able to tell us where these are stored so we can delete them?
I was able to clear it by deleting the DPA.00 folder under C:\Users\rober\AppData\Local\JetBrains\Rider2022.3\resharper-host\local\Transient\Rider\v223\SolutionCaches\<solution>
Could you please also clarify your EF Core version?
Some issues could be caused by https://youtrack.jetbrains.com/issue/DPA-1145 and already fixed.
Thanks!
In my specific case the start up is all over the place and would be hard to exclude. Basically once the first screen is showing, I would like to run some specific actions and get DPA results for that action only.
Alexandra Guk Sorry, I missed the update on this.
I can't see the issue you linked sorry.
We are not using EF, but we are using Microsoft.Data.SqlClient 4.1.0
Rider #RD-223.8617.53, (2022.3.2)
It seems with the latest version, the list is cleared on starting a new debug session so that's all that I needed to make it at least workable.
I agree with OP it would be useful to clear once the application has started. Startup can be very DB intensive so queries take longer normally. We want to then measure (these same queries) once the application has warmed up and the cache is hot to get a true picture of the ongoing performance.