Feat/optimize csv parsing #24
Merged
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
…tests for cache and query
…ntication on api calls
…parameter in SalesforceFactory.new
jbeveland27
reviewed
Apr 18, 2024
jbeveland27
reviewed
Apr 18, 2024
jbeveland27
reviewed
Apr 18, 2024
jbeveland27
approved these changes
Apr 18, 2024
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.
This PR contains many changes to optimize the download and processing of event logs. In particular, requests for CSVs containing event logs are nowstreamed and processed using a generator iterator. In addition, when loading the data into New Relic, logs/events are sent in chunks and gc.collect() is called after each chunk which will attempt to free up memory.
gc.collect()is also run after flushing the cache.