Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add new content ID function #1766
base: main
Are you sure you want to change the base?
Add new content ID function #1766
Changes from 8 commits
0f6ab4d
546d2d9
296fbcf
ebf1a32
65109a8
393eee0
1cf8b69
0424750
dcfc5e0
25eea01
60689cb
e5b68fd
e936834
875313f
09d3762
c457372
85a9d76
10eb07a
0906a3b
060af18
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I honestly doubt that this will work smoothly in production, ordering 118 million advisories using
unique_content_id
, which is an unindexed field is not good idea.#1766 (comment) would be much more practical approach since
id
is an autogenerated primary key field and hence it's already indexed, and we can use this to select the latest or oldest advisory.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
db_index is in models for that! And since we believe there are lots of dupes. I believe index to work fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're adding this
db_index
now. I am not sure how long the index creation itself is going to take.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keeping all that
advisories
in memory is going to be very expensive!Assuming 1 Advisory object ≈ 1000 bytes.
That would mean for 118 million advisories: (118 * 10^6) * 10^3 bytes ≈ 118 GB of memory!.
We should not keep all these advisories in memory. Instead we should bulk update as soon as we reach the batch size.