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.
I'm always frustrated when trying to train forecasting models because it is slow and not using all my CPU cores.
Describe the solution you'd like
Add GPU/CPU Multi-Core Processing for each forecasting method.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
muazhari
changed the title
[FEATURE REQUEST] Add Multi-Core Processing for each forecasting method.
[FEATURE REQUEST] Add GPU / CPU Multi-Core Processing for each forecasting method.
Feb 5, 2023
muazhari
changed the title
[FEATURE REQUEST] Add GPU / CPU Multi-Core Processing for each forecasting method.
[FEATURE REQUEST] Add GPU/CPU Multi-Core Processing for each forecasting method.
Feb 5, 2023
Thanks for the comment. As far as multi-CPU support goes, the underlying API supports it for some models (Prophet, tree models, random cut forest, isolation forest; refer to API documentation for each model), but not others (ARIMA, ETS, spectral residual). GPU is already supported for all deep learning models, and the model will automatically use the GPU if one is available.
We are also investigating GPU support for other models like ARIMA and tree models using Rapids, but this is further out on the roadmap. Let me know if this addresses your questions.
Is your feature request related to a problem? Please describe.
I'm always frustrated when trying to train forecasting models because it is slow and not using all my CPU cores.
Describe the solution you'd like
Add GPU/CPU Multi-Core Processing for each forecasting method.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: