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

Improving Trip Segmentation #953

Conversation

humbleOldSage
Copy link
Contributor

Reducing DB calls. Using more in memory operations.

Replaced loop for DB query with  bulk_write method
Moving transition_Df and motion_df calls upstream in trip_segmentation to improve performance.
@humbleOldSage
Copy link
Contributor Author

Tested. Will fail.

@shankari
Copy link
Contributor

shankari commented Feb 2, 2024

@humbleOldSage can ypu:

  • split the two improvements into separate PRs?
  • add high quality commit messages that (i) quantify the improvements and (ii) link to the issue where you performed the investigation?

This will let me chose which of the improvements to merge. Making server changes can introduce code churn, and I am not convinced that the invalidating raw entry change (which involves a change to the timeseries interface) is worth it.

@humbleOldSage
Copy link
Contributor Author

Sure. I'll create two separate PRs for these two changes.

@humbleOldSage
Copy link
Contributor Author

All the changes here are now split into two separate PRs :

#956 -- for reducing DB calls.
#957. -- for improved invalidation.

There will no longer be any changes here.

@shankari
Copy link
Contributor

shankari commented Feb 5, 2024

@humbleOldSage if this has been replaced by other calls, can you please close this PR?

@humbleOldSage
Copy link
Contributor Author

Sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

2 participants