-
Notifications
You must be signed in to change notification settings - Fork 76
Optimize performance of MSGraphDb generation #1375
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
Optimize performance of MSGraphDb generation #1375
Conversation
I just saw that SQLite has the |
Frankly, no, I have not. Current arrangements reduced the time of filling data to about 0.5 sec that is highly satisfactory. It is very likely the measures like a bulk insert, single transaction, journaling and caching management reproduce the effectiveness of A bottleneck now is downloading (~ 5s) and parsing (~10s) OpenAPI specifications but it happens only once a day (I bet we could increase it with no harm). Additionally contemplated the following measures:
But all of that complicates the code base and does not seem to gain a significant effect. |
Good catch! Thanks for the additional explanation. Let's take the PR as-is. As for the download frequency, we decided on daily so that in case there's a change to the API, you get it quickly, rather than waiting days or weeks. I wonder if there's something like e-tag headers that we could use to decide if we need to download the file. |
It is a great idea. |
Shall I wait with reviewing the PR or will you open another one? |
Either is fine with me. Maybe let's merge the PR and I will prepare a new one on Monday or so. |
Perfect! Thank you! |
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.
Awesome! Nothing to add 👏
#1374