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.

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

Migrate vm_messages to hypertable #1149

Merged
merged 4 commits into from
Mar 2, 2023
Merged

Conversation

birdychang
Copy link
Contributor

No description provided.

@birdychang
Copy link
Contributor Author

Tested in staging db. Took 4 hr to migrate a 50GB table.

@frrist
Copy link
Member

frrist commented Mar 1, 2023

Are stagings resource significantly less than productions?

@birdychang
Copy link
Contributor Author

16 cores v.s. 24 cores, and 122GB v.s. 192GB.

Copy link
Member

@frrist frrist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good once the last review comment is addressed. Please target this change at the frrist/nv18-rc1 branch

@birdychang birdychang changed the base branch from master to frrist/nv18-rc1 March 2, 2023 04:29
@birdychang birdychang changed the base branch from frrist/nv18-rc1 to master March 2, 2023 04:34
@birdychang birdychang merged commit 68bf175 into master Mar 2, 2023
@birdychang birdychang deleted the birdy/migrate_vm_messages branch March 2, 2023 04:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants