This patch addes time trace functionality to have a better understanding
of the analysis times.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Ok. As I said in the chat, when we create a attribute we update it once or we can force a update in the query function, Because of this
the time that it takes to do the update gets added to the time of the attribute that triggered it.
The time data we get doesn't accurately represent the amount of compute that the updateAA of a specific attribute does.
since the cost of updating a attribute when it's first created get's added on top of the time of the attribute that first asked for it.
We can keep track of the update times ourselves, We would stop the timer of the attribute before we start updating another one and restart it when we are done.
We can inject entries directly into the TimeTraceProfiler but that would require some changes with it.
I am not sure if we want to go that route, maybe we land this patch like this for now and if we have hard time interpreting this data, we can add that later ?
I am not sure if we want to go that route, maybe we land this patch like this for now and if we have hard time interpreting this data, we can add that later ?
That sounds like a sensible solution :)
not needed.