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

services/horizon/ingest: Batch Offers insert/updates #3917

Merged
merged 5 commits into from
Sep 14, 2021

Conversation

bartekn
Copy link
Contributor

@bartekn bartekn commented Sep 14, 2021

PR Checklist

PR Structure

  • This PR has reasonably narrow scope (if not, break it down into smaller PRs).
  • This PR avoids mixing refactoring changes with feature changes (split into two PRs
    otherwise).
  • This PR's title starts with name of package that is most changed in the PR, ex.
    services/friendbot, or all or doc if the changes are broad or impact many
    packages.

Thoroughness

  • This PR adds tests for the most critical parts of the new functionality or fixes.
  • I've updated any docs (developer docs, .md
    files, etc... affected by this change). Take a look in the docs folder for a given service,
    like this one.

Release planning

  • I've updated the relevant CHANGELOG (here for Horizon) if
    needed with deprecations, added features, breaking changes, and DB schema changes.
  • I've decided if this PR requires a new major/minor version according to
    semver, or if it's mainly a patch change. The PR is targeted at the next
    release branch if it's not a patch change.

What

This commit adds a new UpsertOffers method (and generic upsertRows) and modifies OffersProcessor to use it.

Close #3913.

Why

The performance of OffersProcessor degraded recently due to number of offers in the network and batching updates should improve the performance of the processor and ingestion overall.

Known limitations

The other processors should probably switch to upsertRows methods. This can be done in a separate PR.

@bartekn bartekn linked an issue Sep 14, 2021 that may be closed by this pull request
@bartekn bartekn marked this pull request as ready for review September 14, 2021 14:04
@bartekn bartekn requested a review from a team September 14, 2021 14:04
@bartekn bartekn merged commit 8732753 into stellar:master Sep 14, 2021
@bartekn bartekn deleted the batch-offer-upserts branch September 14, 2021 20:14
bartekn added a commit that referenced this pull request Sep 14, 2021
This commit adds a new `UpsertOffers` method (and generic `upsertRows`) and
modifies `OffersProcessor` to use it.

The performance of `OffersProcessor` degraded recently due to number of offers
in the network and batching updates should improve the performance of the
processor and ingestion overall.
@@ -14,8 +14,7 @@ type QOffers interface {
GetOffersByIDs(ctx context.Context, ids []int64) ([]Offer, error)
CountOffers(ctx context.Context) (int, error)
GetUpdatedOffers(ctx context.Context, newerThanSequence uint32) ([]Offer, error)
NewOffersBatchInsertBuilder(maxBatchSize int) OffersBatchInsertBuilder
UpdateOffer(ctx context.Context, offer Offer) (int64, error)
UpsertOffers(ctx context.Context, offers []Offer) error
RemoveOffers(ctx context.Context, offerIDs []int64, lastModifiedLedger uint32) (int64, error)
Copy link
Contributor

@2opremio 2opremio Sep 22, 2021

Choose a reason for hiding this comment

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

RemoveOffers can be replaced by UpsertOffers (since a removal is implemented by a tombstone which be set with UpserOffers).

This would save us (up to) a query in each offers processor iteration.

CC @bartekn

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd like to keep it separated for the reasons explained in #3944 (comment).

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.

Batch OffersProcessor database operations
3 participants