[Python] Remarks on result performance (eager vs lazy loading) #430
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stefano-ottolenghi
force-pushed
the
result-remark
branch
from
c83cd26
to
13909dd
Compare
stefano-ottolenghi
changed the title
stefano-ottolenghi
force-pushed
the
result-remark
branch
2 times, most recently
from
ef24b18
to
dde8674
Compare
robsdedude
approved these changes
Jun 12, 2024
| The Neo4j server can retrieve records in batches, and the driver can receive one batch and _wait_ until it has been processed by the application before receiving another one from the server. | ||
| Lazy-loading a result spreads out network traffic and memory usage. | ||
|
|
||
| For convenience, xref:query-simple.adoc[`.execute_query()`] always retrieves all result records at once (it is what the `Eager` in `EagerResult` stands for). |
There was a problem hiding this comment.
Well technically (off to a great start 🙃), you can get .execute_query to discard records instead of streaming them.
There was a problem hiding this comment.
I assume you mean with custom transformers?
| |Lazy loading | ||
|
|
||
| | | ||
| - The server has to read all 250 records from the storage before it can send even the first one the driver (i.e. it takes more time for the client to receive the first record). |
There was a problem hiding this comment.
Really? I expect the server to send the records in batches of the configured batch size.
There was a problem hiding this comment.
Aha. I just kept reading. Eager loading also assumes you don't touch the batch size.
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.