mlcommons / mlcommons/storage

retinanet runs forever without generating I/O

Open
#258 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
203
Forks
67
Avg merge
20m
Merged PRs (30d)
8

Description

I am using the new_training_yamls branch. My system has 1TB of memory so it wanted me to create 8559921 files during datagen. Unfortunately the training run ran over the weekend at 100% CPU but it never finished and there was practically no I/O... not too good for a storage test.

I limited it to 100,000 files combined with --client-host-memory-in-gb 1 and it ran fairly quickly, e.g.:

781 steps completed in 91.85 s

However, bumping it up to 1,000,000 files took much more than 10x longer:

3906 steps completed in 4376.46 s

The completed runs had all zeroes as well:

[METRIC] Number of Simulated Accelerators: 4
[METRIC] Training Accelerator Utilization [AU] (%): 0.0000 (0.0000)
[METRIC] Training Throughput (samples/second): 0.0000 (0.0000)
[METRIC] Training I/O Throughput (MB/second): 0.0000 (0.0000)
[METRIC] train_au_meet_expectation: fail

So the questions I have are:

  1. Is this the right place to ask this question?
  2. Am I using the right code?
  3. What should I try next to make the retinanet test work?

Thanks,
Mark

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the new_training_yamls branch and the datagen entry point for the retinanet test. Reproduce the reported runs with --client-host-memory-in-gb set to 1 and compare 100,000 versus 1,000,000 files. Done means the run completes predictably and reports nonzero training and I/O throughput.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.