google / google/gapid

It takes a long time to open GAPID trace

Open
#3,399 10 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.2k
Forks
329
PR merge metrics
No merged PRs in 30d

Description

Dear sirs,
I encountered a loading problem when I replay GAPID trace:
1.A 0.5 minute trace with file size 117M (809 frames), it needs 5 minute to load all the frames.
2.A 1 minute trace with file size 160M(2480 frames),Frame#0-Frame#1095 done in 25 minutes, the other frames are always in loading, we stop to wait the frame loading at last.
3.A 2 minute trace with file size 258M(5154 frames) is always in loading state,and we stop it 1 hour's later.
Is there any way to catch the trace with small file size or shall we divide a big trace to several small ones(eg: When I catch a trace,the trace will be saved in several files,every file is as small as I can open it quickly).
My GAPID version is 1.6.1
Thanks for your help.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.