-
Notifications
You must be signed in to change notification settings - Fork 10.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate speeding up MockServer()
#6255
Comments
Looks like the main problem I experience is because on this machine trying to resolve an invalid domain (which we do on every import of Line 31 in 532cc8a
|
The next step is doing something about the coverage-introduced slowness, it takes about 2 seconds to initialize mockserver under |
Without coverage and h2 the start up time of mockserver here is about 0.4s, under |
On my machine, with coverage enabled and
h2
installed (both of these things add significant additional time), a single call oftests.mockserver.MockServer()
, at least inFeedExportTest.run_and_export()
, takes up to 6.5s, which is likely the main reason why our tests, and especially feed export tests (which start the mockserver many times per test function viaassertExported*()
and in the worst caseassertExported()
) are so slow. The slowest test,tests/test_feedexport.py::FeedExportTest::test_export_feed_export_fields
, actually reaches the 120s limit here because it calls MockServer() 2*2*6=24 times.The text was updated successfully, but these errors were encountered: