Profiles / #6
Passed Run of Oct 20, 18:17
short_tests 5 tests finished faster than one sample (1ms), so they have timings but no breakdown. That's expected for tests this fast.
Wall time
32.48 s
1 worker
Test time
26.36 s
sum of test durations
Tests
235
235 passed
Profiler
tachyon
1000 Hz ·
22,030 samples · Python 3.15.0 · flakytest 2026.0b1
Peak memory
171 MB
test process
Where the time goes
Test time by category- Database11.90 s
- Libraries6.06 s
- Migrations2.61 s
- Password hashing1.91 s
- DB schema1.65 s
- Templates590 ms
- Serialization461 ms
- App code403 ms
- Imports292 ms
- Unsampled146 ms
- pytest142 ms
- Deep copies120 ms
- Factories34 ms
- Test code21 ms
- Waiting19 ms
- Cache8 ms
- Mocking7 ms
- Logging4 ms
Session timeline
Tests
24.94 s
Startup
5.82 s
Collection
289 ms
Between tests
761 ms
Session teardown
494 ms
Test phases
Setup 5.38 s
Call 20.83 s
Teardown 158 ms
Fix next
Ranked by the time each fix saves per run
1
Run tests in parallel on all 2 CPUs
Tests run one at a time: 26.4s of test time on a 2-CPU machine. With pytest-xdist this could take about 13.2s.
High
Parallelism
13.18 s
per run
Fix: pip install pytest-xdist, then run pytest -n auto (add it to addopts, or only in CI). pytest-django creates a separate test database per worker automatically.
Details
Tests must not share state: files in fixed paths, ports, a shared database without per-worker names, or module globals. Run with -p randomly first to shake out order dependencies.
2
Use plain static file storage in tests
Static file storage/manifest handling costs 11.5s.
High
App code
11.52 s
per run
Fix: In test settings use STORAGES["staticfiles"] = {"BACKEND": "django.contrib.staticfiles.storage.StaticFilesStorage"} so templates don't need a manifest.
Details
Where:
- apps/api/tests.py:487 ProfileUploadTest.upload · 623 ms
- apps/mcp/tests.py:66 McpTest.post · 582 ms
- ft/tests.py:203 TestAccountSettings.test_change_password · 420 ms
- apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 291 ms
- apps/projects/urls.py:498 project_profile · 251 ms
- ft/tests.py:159 TestAccountPages.test_signup · 236 ms
- apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 215 ms
- ft/tests.py:96 TestTrubleshootingPage.test_troubleshooting · 213 ms
- ft/tests.py:198 TestAccountSettings.test_change_password · 206 ms
- apps/api/tests.py:58 TestInvalidIngest.test_ingest_invalid · 199 ms
Most affected tests:
- ft/tests.py::TestAccountSettings::test_change_password
- apps/orgs/tests.py::SignupTest::test_signing_up_creates_an_organization
- apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
- ft/tests.py::TestAccountPages::test_signup
- apps/api/tests.py::ProfileUploadTest::test_missing_parts_mark_the_profile_incomplete
- ft/tests.py::TestTrubleshootingPage::test_troubleshooting
- apps/projects/tests.py::ProfilePagePaginationTest::test_slowest_tests_first_then_the_next_page
- apps/api/tests.py::TestInvalidIngest::test_ingest_invalid
3
Disable django-debug-toolbar in tests
django-debug-toolbar is installed in the test settings and costs 6.7s.
High
App code
6.75 s
per run
Fix: Only add debug_toolbar to INSTALLED_APPS and MIDDLEWARE when not testing (e.g. `if DEBUG and not TESTING:`).
Details
Where:
- ft/tests.py:203 TestAccountSettings.test_change_password · 420 ms
- apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 276 ms
- apps/projects/urls.py:498 project_profile · 251 ms
- ft/tests.py:159 TestAccountPages.test_signup · 236 ms
- apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 215 ms
- ft/tests.py:198 TestAccountSettings.test_change_password · 206 ms
- apps/projects/tests.py:88 IndexPageTest.test_index_page · 146 ms
- apps/projects/urls.py:49 find_project · 128 ms
- apps/orgs/views.py:33 org_shell · 125 ms
- apps/projects/urls.py:40 can_manage_project · 118 ms
Most affected tests:
- ft/tests.py::TestAccountSettings::test_change_password
- apps/orgs/tests.py::SignupTest::test_signing_up_creates_an_organization
- apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
- ft/tests.py::TestAccountPages::test_signup
- apps/api/tests.py::ProfileUploadTest::test_missing_parts_mark_the_profile_incomplete
- apps/projects/tests.py::IndexPageTest::test_index_page
- apps/projects/tests.py::ProfilePagePaginationTest::test_slowest_tests_first_then_the_next_page
- apps/api/tests.py::ProfileUploadTest::test_upload_adds_migrations_per_worker_insight
4
Repeated queries (N+1) in the code under test
27 tests run the same query 10+ times, e.g. 180x in test_seed_demo. N+1 queries slow the tests and production alike.
High
Database
3.46 s
per run
Fix: Django: fetch related rows in one query with select_related() for foreign keys and prefetch_related() for reverse/many-to-many relations, then lock the count in with assertNumQueries (or pytest-django's django_assert_num_queries).
Details
This changes application code, so it speeds up production too; the tests stay as they are.
- 180x in test_seed_demo: SELECT "projects_test"."id", "projects_test"."name", "projects_test"."project_id", "projects_test"."slug", "projects_test"."date_last_run", "projects_test"."date_first_seen", "projects_test"."first_commit_id", "projects_test"."muted" FROM "projects_test" WHERE ("projects_test"."name" = %s AND "proj…
- 22x in test_dashboard_filters: SELECT "projects_environment"."id", "projects_environment"."project_id", "projects_environment"."name", "projects_environment"."kind", "projects_environment"."provider", "projects_environment"."details", "projects_environment"."date_first_seen", "projects_environment"."date_last_seen" FROM "project…
- 21x in test_configure_page: SELECT "projects_profile"."id", "projects_profile"."project_id", "projects_profile"."number", "projects_profile"."environment_id", "projects_profile"."session_id", "projects_profile"."run_id", "projects_profile"."commit_id", "projects_profile"."ingest_id", "projects_profile"."external_id", "project…
- 20x in test_index: SELECT "django_content_type"."model" AS "model" FROM "django_content_type" WHERE "django_content_type"."app_label" = %s
- 20x in test_daily_stats_count_a_profile_once_every_part_is_in: SELECT "projects_profilepart"."id", "projects_profilepart"."profile_id", "projects_profilepart"."index", "projects_profilepart"."count", "projects_profilepart"."checksum", "projects_profilepart"."status", "projects_profilepart"."error", "projects_profilepart"."tests_count", "projects_profilepart"."…
Most affected tests:
- apps/projects/tests.py::SeedDemoCommandTest::test_seed_demo
- apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
- apps/projects/tests.py::ProjectPagesTest::test_configure_page
- apps/api/tests.py::TestApiIndex::test_index
- apps/api/tests.py::ProfileUploadTest::test_daily_stats_count_a_profile_once_every_part_is_in
- apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
- apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress
5
Make the test database server skip durability work
Tests spend 16.1s (61%) in the database. Test databases don't need to survive a crash, so the server can skip flushing to disk.
High
Database
3.23 s
per run
Fix: For a PostgreSQL test server (Docker/CI service) start it with -c fsync=off -c synchronous_commit=off -c full_page_writes=off, and put its data directory on tmpfs; for MySQL use --innodb-flush-log-at-trx-commit=0 --skip-log-bin. Never on a server with data you need.
Details
Only affects crash safety of the throwaway test server; query behaviour is identical.
Where:
- apps/projects/models.py:466 Profile.save · 323 ms
- apps/projects/profiles.py:313 write_snapshots · 259 ms
- apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 213 ms
- apps/projects/environments.py:63 get_or_create_environment · 204 ms
- apps/projects/tests.py:953 ProjectPagesTest.setUp · 200 ms
- apps/api/tests.py:76 IngestStartEndpointTest.join_workers · 195 ms
- apps/projects/profiles.py:458 write_perfs · 185 ms
- apps/projects/rollups.py:88 add_perfs · 171 ms
- apps/projects/models.py:230 TestManager.upsert · 159 ms
- apps/api/tests.py:73 IngestStartEndpointTest.setUp · 149 ms
Most affected tests:
- apps/api/tests.py::TestApiIndex::test_index
- apps/projects/tests.py::SeedDemoCommandTest::test_seed_demo
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
- apps/projects/tests.py::ProjectPagesTest::test_configure_page
- apps/projects/tests.py::ProfilePagePaginationTest::test_slowest_tests_first_then_the_next_page
- apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
- apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
6
pytest takes a long time before the first test runs
Startup takes 5.8s and collection 289ms on every run, even when you only run one test.
Medium
Imports
2.44 s
per run
Fix: Set testpaths and norecursedirs (node_modules, .venv, build, docs) so pytest doesn't walk unrelated directories; move heavy imports out of module level in test files and conftest.py into fixtures; check `python -X importtime -m pytest --collect-only -q` for the slowest imports.
7
Stop re-running migrations on every test run
Migrations take 2.6s per run, before the first test can start.
Medium
Migrations
2.35 s
per run
Fix: Run with --reuse-db (add it to addopts in pytest.ini/pyproject) so the test database survives between runs; pass --create-db when migrations change. If no test depends on data migrations, --nomigrations builds the schema straight from the models, which is faster still.
Details
CI should still build the database from scratch (no --reuse-db) so broken migrations are caught.
Where:
- apps/projects/migrations/0012_backfill_session_environments.py:30 backfill · 6 ms
- apps/projects/migrations/0022_backfill_organizations.py:48 forwards · 5 ms
- apps/projects/migrations/0025_backfill_slugs_and_numbers.py:28 forwards · 3 ms
- apps/projects/migrations/0016_profile_parts.py:9 move_documents · 3 ms
- apps/projects/migrations/0004_project_created_by_project_date_created_and_more.py:12 add_created_by_to_project · 2 ms
- apps/projects/migrations/0009_auto_20240218_1217.py:12 create_mute_objects · 2 ms
- apps/projects/migrations/0012_backfill_session_environments.py:24 backfill · 2 ms
- apps/projects/migrations/0014_backfill_session_counts.py:23 backfill · 2 ms
- apps/projects/migrations/0015_store_compressed_documents_as_is.py:12 external_storage · 2 ms
- apps/projects/migrations/0016_profile_parts.py:24 external_storage · 2 ms
Most affected tests:
- apps/api/tests.py::TestApiIndex::test_index
8
Use a fast password hasher in tests
1.9s (7% of test time) is spent hashing passwords. Slow hashing protects real passwords; in tests it only burns CPU.
Medium
Password hashing
1.81 s
per run
Fix: In your test settings set PASSWORD_HASHERS = ["django.contrib.auth.hashers.MD5PasswordHasher"] (currently PBKDF2PasswordHasher).
Details
Only change the hasher in test settings. Tests that assert on a specific hash format need updating.
Where:
- ft/tests.py:203 TestAccountSettings.test_change_password · 413 ms
- apps/orgs/tests.py:194 SuperuserTest.test_superusers_can_open_any_project_but_dont_list_them · 229 ms
- apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 224 ms
- ft/tests.py:230 TestAccountSettings.test_projects_only_lists_your_own_even_for_superusers · 223 ms
- ft/tests.py:159 TestAccountPages.test_signup · 219 ms
- ft/tests.py:198 TestAccountSettings.test_change_password · 202 ms
- ft/tests.py:213 TestAccountSettings.test_change_password · 201 ms
- ft/tests.py:175 TestAccountSettings.setUpTestData · 198 ms
Most affected tests:
- ft/tests.py::TestAccountSettings::test_change_password
- apps/orgs/tests.py::SuperuserTest::test_superusers_can_open_any_project_but_dont_list_them
- apps/orgs/tests.py::SignupTest::test_signing_up_creates_an_organization
- ft/tests.py::TestAccountSettings::test_projects_only_lists_your_own_even_for_superusers
- ft/tests.py::TestAccountPages::test_signup
9
Use TestCase instead of TransactionTestCase
1.4s goes to flushing every table after tests in 11 TransactionTestCase / transaction=True / live_server tests.
Medium
DB schema
1.25 s
per run
Fix: Use django.test.TestCase (or @pytest.mark.django_db without transaction=True): it wraps each test in a transaction and rolls back instead of truncating every table. Keep TransactionTestCase only for tests that need real commits (on_commit hooks can use TestCase.captureOnCommitCallbacks).
Details
Tests that rely on commit behaviour, multiple connections or a live server still need a transactional test case.
Most affected tests:
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_valid
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_with_git
- apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
- apps/api/tests.py::ProfileUploadLockTest::test_upload_while_a_part_is_being_processed
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress
- apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
10
Tests open new database connections over and over
Connecting to the database takes 959ms.
Low
Database
767 ms
per run
Fix: Reuse connections: create the engine once per session (not per test) and keep the default pool (NullPool reconnects on every checkout); in Django avoid closing connections in tests (connection.close()/close_old_connections).
Details
Where:
- apps/api/tests.py:76 IngestStartEndpointTest.join_workers · 175 ms
- apps/api/tests.py:73 IngestStartEndpointTest.setUp · 95 ms
- apps/api/tasks.py:266 warm_reports · 67 ms
- apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 51 ms
- apps/api/tests.py:306 IngestStartEndpointTest.test_details_are_kept_for_failures_only · 14 ms
- apps/api/tests.py:235 IngestStartEndpointTest.test_ingest_progress_before_start · 13 ms
- apps/api/tests.py:287 IngestStartEndpointTest.test_all_test_status_types · 12 ms
- apps/api/tests.py:257 IngestStartEndpointTest.test_ingest_end_after_progress · 12 ms
- apps/api/tests.py:331 IngestStartEndpointTest.test_results_are_counted_and_the_payload_dropped · 11 ms
- apps/api/tests.py:988 ProfileUploadQueueTest.test_upload_is_processed_by_the_worker · 11 ms
Most affected tests:
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
- apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped
- apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
- apps/api/tests.py::ProfileUploadQueueTest::test_upload_is_processed_by_the_worker
- apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
- apps/orgs/tests.py::SettingsTest::test_create_another_organization
11
Create shared test data in setUpTestData instead of setUp
setUp() runs before every test and takes 887ms in total (db 803ms, library 59ms, factories 12ms) in 13 classes: SettingsTest (3 tests), ProjectsPageTest (5 tests), ProjectEditPage (6 tests), ProjectDeletePage (4 tests).
Low
Database
621 ms
per run
Fix: Move object creation that tests only read from setUp() into `@classmethod def setUpTestData(cls)`: it runs once per class and each test still sees the original rows (TestCase rolls back to a savepoint).
Details
Since Django 3.2 attributes assigned in setUpTestData are deep-copied per test, so in-memory changes don't leak between tests. Keep objects a test modifies in the database (or re-fetches) as before.
Where:
- apps/projects/tests.py:953 ProjectPagesTest.setUp · 218 ms
- apps/api/tests.py:73 IngestStartEndpointTest.setUp · 161 ms
- apps/projects/tests.py:142 ProjectEditPage.setUp · 69 ms
- apps/projects/tests.py:218 ProjectCreatePage.setUp · 49 ms
- apps/projects/tests.py:268 ProjectRunsPage.setUp · 49 ms
- apps/projects/tests.py:1375 MemoryTest.setUp · 45 ms
- apps/projects/tests.py:337 ProjectTestsPage.setUp · 43 ms
- apps/projects/tests.py:100 ProjectsPageTest.setUp · 43 ms
- apps/orgs/tests.py:167 SettingsTest.setUp · 38 ms
- apps/projects/tests.py:187 ProjectDeletePage.setUp · 37 ms
Most affected tests:
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_multiple_sessions
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_with_git
- apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_valid
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
- apps/orgs/tests.py::SettingsTest::test_create_another_organization
- apps/api/tests.py::ProfileUploadLockTest::test_upload_while_a_part_is_being_processed
Tests
1–200 of 235, slowest first · click a column to sort this page
Page 1 of 2
Next
Memory
The test process peaked at 198 MBSlowest fixtures
Exact setup time across the session| Fixture | Scope | Calls | Total |
|---|---|---|---|
| _django_setup_unittest | class | 50 | 2.93 s |
| django_db_setup | session | 1 | 2.91 s |
| _unittest_setUpClass_fixture_ProjectPagesTest | class | 1 | 304 ms |
| _unittest_setUpClass_fixture_RealProfileDocumentTest | class | 1 | 288 ms |
| _unittest_setUpClass_fixture_ProfilePagePaginationTest | class | 1 | 245 ms |
| _unittest_setUpClass_fixture_TestAccountSettings | class | 1 | 210 ms |
| _unittest_setUpClass_fixture_McpTest | class | 1 | 196 ms |
| _unittest_setUpClass_fixture_AnalyticsTest | class | 1 | 185 ms |
| _unittest_setUpClass_fixture_MemoryTest | class | 1 | 94 ms |
| _unittest_setUpClass_fixture_StorageTest | class | 1 | 86 ms |
| _unittest_setUpClass_fixture_FlakyReportTest | class | 1 | 69 ms |
| _unittest_setUpClass_fixture_LegacyUrlTest | class | 1 | 64 ms |
| _unittest_setUpClass_fixture_FlakyReportCacheTest | class | 1 | 52 ms |
| _unittest_setUpClass_fixture_SettingsTest | class | 1 | 28 ms |
| _unittest_setUpClass_fixture_ProjectRunPage | class | 1 | 20 ms |