You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
run the --import and --analyze commands on GarminDB, take too long to complete, even for just --latest option.
Describe the solution you’d like
I would like the --import and --analyze commands to be multi-threaded or multi-processed, so that they can utilize the available CPU cores and speed up the execution. This would make GarminDB more efficient and responsive, and save me time
Describe alternatives you’ve considered
N/A
Additional context
the commands only use one CPU core and take several minutes to finish. I think this can be improved by implementing multi-threading or multi-processing.
The text was updated successfully, but these errors were encountered:
shemeshg
changed the title
Multi-threading or multi-processing for --import and --analyze commands
Feature request: Multi-threading or multi-processing for --import and --analyze commands
Feb 2, 2024
Is your feature request related to a problem? Please describe.
run the --import and --analyze commands on GarminDB, take too long to complete, even for just --latest option.
Describe the solution you’d like
I would like the --import and --analyze commands to be multi-threaded or multi-processed, so that they can utilize the available CPU cores and speed up the execution. This would make GarminDB more efficient and responsive, and save me time
Describe alternatives you’ve considered
N/A
Additional context
the commands only use one CPU core and take several minutes to finish. I think this can be improved by implementing multi-threading or multi-processing.
The text was updated successfully, but these errors were encountered: