mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pedro Larroy <pedro.larroy.li...@gmail.com>
Subject Improving and rationalizing unit tests
Date Mon, 16 Oct 2017 12:56:21 GMT
Hi

Some of the unit tests are extremely costly in terms of memory and compute.

As an example in the gluon tests we are loading all the datasets.

test_gluon_data.test_datasets

Also running huge networks like resnets in test_gluon_model_zoo.

This is ridiculously slow, and straight impossible on some embedded /
memory constrained devices, and anyway is making tests run for longer than
needed.

Unit tests should be small, self contained, if possible pure (avoiding this
kind of dataset IO if possible).

I think it would be better to split them in real unit tests and extended
integration test suites that do more intensive computation. This would also
help with the feedback time with PRs and CI infrastructure.


Thoughts?

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message