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

Optimization - avoid deserializing the graph result twice #30

Merged
merged 1 commit into from
Aug 15, 2024

Conversation

meslubi2021
Copy link
Owner

@meslubi2021 meslubi2021 commented Aug 15, 2024

The GraphResult constructor already initializes the ResultDictionary (from the underlying ResultContainer dictionary) There’s no need to deserialize the data again and assign it, in case it was already done. This saves both execution time and unneeded GC.

Thanks for proposing a pull request!

To help us review the request, please complete the following:

  • sign contributor license agreement
  • I've ensured that all existing tests pass and added tests (when/where necessary)
  • I've updated the documentation (when/where necessary) and Changelog (when/where necessary)
  • I've added the proper label to this pull request (e.g. bug for bug fixes)

Pull Request Details

Describe what you accomplished in this pull request (for example, what happens before the change, and after the change)

Test Plan

Test Plan: Add your test plan here

The GraphResult constructor already initializes the ResultDictionary (from the underlying ResultContainer dictionary)
There’s no need to deserialize the data again and assign it, in case it was already done. This saves both execution time and unneeded GC.
@meslubi2021 meslubi2021 self-assigned this Aug 15, 2024
@meslubi2021 meslubi2021 merged commit dff1920 into meslubi2021:main Aug 15, 2024
5 of 42 checks passed
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.

2 participants