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

postgres table sharding POC #150

Open
InoMurko opened this issue Oct 19, 2020 · 2 comments
Open

postgres table sharding POC #150

InoMurko opened this issue Oct 19, 2020 · 2 comments
Assignees

Comments

@InoMurko
Copy link
Contributor Author

So the goal of this exercise is to see if PG internal sharding (partitioning) is helpful in splitting up the transaction table.
We would like to se:

  1. local docker compose setup
  2. demonstrable test with increased performance over the current
  3. estimation of any necessary code changes and it's implications

@InoMurko InoMurko changed the title postgres table sharding postgres table sharding POC Oct 19, 2020
@mederic-p mederic-p removed their assignment Oct 29, 2020
@InoMurko
Copy link
Contributor Author

InoMurko commented Dec 7, 2020

The table that gets hit most and we would like to see it being more performant is Engine.DB.Output and perhaps also Engine.DB.Transaction. But at least for the Engine.DB.Transaction we have plans to prune it if it's going to be doable.

So these two tables should be your focus!

cc @pgebal @mederic-p if you have any more inputs since you've been doing some performance measurements, please leave them here for @DanielaIvanova !

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

No branches or pull requests

3 participants