-
Notifications
You must be signed in to change notification settings - Fork 11
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
Improve file extractor performance #268
Comments
The described behavior partially explains the behavior observer in issue #261 |
I am currently looking into the following approach (see branch: enh NB this is in an experimental state):
The current implementation consists of three components, a server, a client, and a patcher ServerCurrently, a simple HTTP-server that accepts commands from localhost, executes them, if the result was not yet calculated, and returns the cached result. ClientA simple request-based client that provides a remote-execution call that is similar to PatcherA module that provides a method that patches the |
Dropping the server approach for
|
During a single file-level metadata extraction for legacy extractors 17 (seventeen) subprocess calls to
git
are executed, 5 of which are executed twice.Here is a list of the subprocess calls:
As a first candidate for improvement, a number of git-calls stem from the following function:
The text was updated successfully, but these errors were encountered: