Skip to content
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.

Sign up for GitHub

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

Jump to bottom

server: TestAdminAPIEvents takes too long to run in external-process mode #142381

Open
shubhamdhama opened this issue Mar 6, 2025 · 0 comments
Open

server: TestAdminAPIEvents takes too long to run in external-process mode #142381

shubhamdhama opened this issue Mar 6, 2025 · 0 comments
Labels
C-investigation Further steps needed to qualify. C-label will change.

Comments

@shubhamdhama
Copy link
Contributor

shubhamdhama commented Mar 6, 2025 •
edited
Loading

When TestAdminAPIEvents runs in external-process mode, the first test case takes around 40 seconds, while the rest run within the usual time. We need to investigate why this initial warm-up takes so long.

Example:

external-process mode

--- PASS: TestAdminAPIEvents (41.97s)
    --- PASS: TestAdminAPIEvents/events?type=drop_database (35.26s)
    --- PASS: TestAdminAPIEvents/events?type=create_database (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=drop_table (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=create_table (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=set_cluster_setting (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=set_cluster_setting&limit=0&unredacted_events=true (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=create_table&limit=0 (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=create_table&limit=-1 (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=create_table&limit=2 (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=node_join (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=node_restart (0.00s)
    --- PASS: TestAdminAPIEvents/events (0.00s)

vs

shared-process mode

--- PASS: TestAdminAPIEvents (6.57s)
    --- PASS: TestAdminAPIEvents/events?type=drop_database (0.07s)
    --- PASS: TestAdminAPIEvents/events?type=create_database (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=drop_table (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=create_table (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=set_cluster_setting (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=set_cluster_setting&limit=0&unredacted_events=true (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=create_table&limit=0 (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=create_table&limit=-1 (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=create_table&limit=2 (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=node_join (0.00s)
    --- PASS: TestAdminAPIEvents/events?type=node_restart (0.00s)
    --- PASS: TestAdminAPIEvents/events (0.00s)

Related: #138912

Jira issue: CRDB-48302
@shubhamdhama shubhamdhama added the C-investigation Further steps needed to qualify. C-label will change. label Mar 6, 2025
@shubhamdhama shubhamdhama mentioned this issue Mar 6, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-investigation Further steps needed to qualify. C-label will change.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@shubhamdhama