-
Notifications
You must be signed in to change notification settings - Fork 2
#617: Writing out json is very slow with large files #618
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
Open
cwschilly
wants to merge
6
commits into
develop
Choose a base branch
from
617-writing-out-json-is-very-slow-with-large-files
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
f04473f
#617: tmp fix: add timer to all methods and use comm param
cwschilly 966684c
#617: tmp fix: do not use mp for writing JSON
cwschilly e745016
#617: separate timer decorator into own file; clean up writer code
cwschilly 5d840ca
#617: add default for including comms in JSON
cwschilly b198cd6
#617: remove unused method
cwschilly 4bd7858
#617: experiment with thread concurrency
cwschilly File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| import time | ||
| import logging | ||
| import functools | ||
|
|
||
| def timer(method): | ||
| @functools.wraps(method) | ||
| def wrapper(self, *args, **kwargs): | ||
| """Times the execution of the decorated function.""" | ||
| # Time the function duration | ||
| start = time.time() | ||
| res = method(self, *args, **kwargs) | ||
| end = time.time() | ||
| dur = end - start | ||
|
|
||
| # Get a logger instance (stacklevel=2 uses the logger from the function being decorated) | ||
| logger = logging.getLogger(self.__class__.__module__) | ||
| logger.debug(f"{method.__name__}: {dur:.4f} s", stacklevel=2) | ||
|
|
||
| return res | ||
| return wrapper |
Oops, something went wrong.
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.
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.
Does it make sense to default to
Truehere? Or should users opt-in to writing comms?