v0.4.0: `ZeusMonitor`

What's New

• Just measuring energy with Zeus has been non-trivial. Now, ZeusMonitor is the only way to measure time and energy consumed by an arbitrary set of GPUs from executing an arbitrary range of code. There should be one-- and preferably only one --obvious way to do it.
  • ZeusDataLoader was refactored to build around ZeusMonitor.
  • ZeusMonitor is quite thoroughly tested now.

v0.3.0: `ZeusMonitorContext` for in-training-loop profiling

What's New

• ZeusMonitorContext allows users to profile their per-iteration energy and time consumption.
  • It's aimed for those who would like to get a feel for the energy consumption of their DNN training job with a couple additional lines (as opposed to modified lines).
  • Documentation and integration example: here

v0.2.2

Bug Fix

• Fixed a bug that made all Zeus monitors monitor the same GPU (index 0) in DP mode (#10)

v0.2.1

Bug fix

• Fixed a bug where power limit profiling did not carry over to the next epoch when the dataset has less numbers of batches (#7).

v0.2.0: Single-Node Data Parallel Support

New Features

• Single-node multi-GPU data parallel training support added (#2)
• zeus_monitor is built at Docker image build time and baked into the image (#6)

Breaking Changes

• ZeusDataLoader's profile window for each power limit is now based on the number of iterations, not time. (#2)
  • This was done to ease synchronization between GPUs while profiling power limits.
  • The ZEUS_PROFILE_PARAMS environment variable is now parsed as a comma separated string of the number of warmup and measure iterations.
  • ZeusMaster's constructor now takes arguments profile_warmup_iters and profile_measure_iters.

v0.1.0

First official release of Zeus!

• Support for single-GPU training is stable.