Skip to content

No setting to allow collecting the first trace early. #91888

@albanD

Description

@albanD

The default schedule behavior is to 'wait' immediately following the skip_first steps. As a consequence, if we want to wait 5k steps between traces, the earliest possible trace we can collect is after 5k steps. We'd like to be able to record a trace early in training, like at step 100, and then subsequently once every 5k steps.

cc @robieta @chaekit @aaronenyeshi @ngimel @nbcsm @guotuofeng @guyang3532 @gaoteng-git @tiffzhaofb

Metadata

Metadata

Assignees

Labels

oncall: profilerprofiler-related issues (cpu, gpu, kineto)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions