-
Notifications
You must be signed in to change notification settings - Fork 100
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
Running out of RAM in 0.6.3 #210
Comments
Thanks for the quick and specific identification. Let me run it and see. |
--- some running later --- |
--- after another run --- |
Scalable is a much larger group of transformers than superfast is, so should be more accurate. but it looks like I have more work to do still in chasing down parameter combinations that lead to too much memory. I suspect it is in the "AnomalyRemoval" --> "RegressionFilter" that is causing the problems |
I probably can't help you with this, but if there's a way I can contribute, let me know! |
Upgraded to 0.6.3 today and also updated all dependencies.
Using AutoTS 0.6.3 model.fit() runs fine like it did before on the same data set. Average memory usage is less than 4GB throughout model generations and validations, except for this model which tries to allocate 49GB of RAM and therefore crashes AutoTS:
{"model_number": 386, "model_name": "MultivariateMotif", "model_param_dict": {"window": 10, "point_method": "midhinge", "distance_metric": "hamming", "k": 20, "max_windows": 10000}, "model_transform_dict": {"fillna": "SeasonalityMotifImputerLinMix", "transformations": {"0": "bkfilter", "1": "AlignLastValue", "2": "AlignLastValue", "3": "bkfilter"}, "transformation_params": {"0": {}, "1": {"rows": 7, "lag": 1, "method": "additive", "strength": 1.0, "first_value_only": false}, "2": {"rows": 1, "lag": 28, "method": "additive", "strength": 1.0, "first_value_only": false}, "3": {}}}}
This never happened on many test runs on 0.6.2 with the same AutoTS model and dataset.
Is this a bug or can I prevent this validation from causing a crash somehow?
Would it be possible to implement a precaution in a future version of AutoTS that skips validation methods or models when running out of RAM?
The text was updated successfully, but these errors were encountered: