search

ezmsg-org / ezmsg

Pure-Python DAG-based high-performance SHM-backed pub-sub and multi-processing pattern
https://ezmsg.readthedocs.io/en/latest/
MIT License
10 stars 5 forks source link

Tests run too slowly #3

Closed griffinmilsap closed 1 year ago

griffinmilsap commented 1 year ago

We may be over-testing in some units, especially with excessive use of pytest.parametrize to create huge matrices of test cases. It'd be great to target ~1 min for all signal processing tests to conclude.

griffinmilsap commented 1 year ago

Windows tests were taking ~7-12 minutes prior to 3.2.2. I noticed SHMServer and GraphServer were taking a VERY long time to start up -- IDK what it is about spawning daemon subprocesses in Windows, but there's some SIGNIFICANT overhead. I've addressed this for tests by starting the ezmsg core servers using ezmsg start before running the tests, then shutting them down with ezmsg shutdown

griffinmilsap commented 1 year ago

With recent changes in the dev branch, we no-longer spin up new processes for SHMServer and GraphServer. These now spin up in microseconds, even in Windows; and testing now concludes in a minute or so. Closing this for now.