We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The database can get very large very quickly. We need to look at the data structure.
A summary of a suggestion from Discord: it's likely that the biggest amount of data we are storing is the magnet links.
In a magnet link the majority of the text is going to be the trackers.
If we make a trackers table for each tracker we encounter and then link back to it we can deconstruct and reconstruct the magnet links in the code.
Using this method we could see a significant reduction in the size of the stored data.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The database can get very large very quickly. We need to look at the data structure.
A summary of a suggestion from Discord: it's likely that the biggest amount of data we are storing is the magnet links.
In a magnet link the majority of the text is going to be the trackers.
If we make a trackers table for each tracker we encounter and then link back to it we can deconstruct and reconstruct the magnet links in the code.
Using this method we could see a significant reduction in the size of the stored data.
The text was updated successfully, but these errors were encountered: