| Re: [tracecompass-dev] Reindexing trace file and rebuilding the state system during analysis |
|
The state history on disk is designed to be immutable. This is an interesting use case, it leads to maybe looking into partial state system, there was some work here:
This would give the notion of checkpoints and a cascaded secondary state system. That being said, it would not be ideal as the trace would be read twice. Can we help you making the trace handling faster maybe?
Basically, more info, if you're allowed to share, would help.
Matthew
From: tracecompass-dev <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of Alex Doan <vadoan@xxxxxxxxxxxxxx>
Sent: Tuesday, February 28, 2023 8:55 AM To: tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx> Subject: [tracecompass-dev] Reindexing trace file and rebuilding the state system during analysis Hi, I am currently working on a feature where the trace would be analyzed at a higher resolution on zoom. Right now I have a workaround that is to open the trace file at very high resolution at the start then lower the resolution after the fact, however this have the downside of making analysis takes significantly longer, and limit the maximum resolution I can produce due to the performance.
Is there a way to change state system attribute mid analysis? Any help would be appreciated.
Thank you,
Alex This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. |