Hi. Sorry for bothering. Quick question: I tried running auto_arima_prophet in the same setup we have used Prophet for our forecasting and we have seen that auto_arima_prophet has 7x the running time for fit and predict, that Prophet has. Is there something we are doing wrong ? MSE is still 10% better for ARIMA, but still, I find it weird.

Hi! For production settings we recommend using the forecast method instead of the fit predict ones.

@Max (Nixtla) https://github.com/Nixtla/statsforecast/tree/main/experiments/arima_prophet_adapter -> I see you here using fit and then make future dataframe and then predict. Could you be more specific what you mean by using forecast?

Hi Andrei, I will try to give you a complete answer soon.

Yes, I will ask the guys from our team to send over the code. But most plainly put. compared directly Autoarimaprophet with prophet, with uncert intervals = 0 and some fut regressors. The dataset is weekly and kinda small.

Is there a specific reason you want to compare Prophet and AutoArima? I would highly suggest finding appropriate models for each combination of series (e.g. product and store). For some series, sparse models like ADIDA or Croston might be very successful.

we have weekly data and it`s not sparse. And we want to use it because 1. we have seasonality and trend + maybe some holidy effect (product demand forecasting). we have some future regressors and dataset is not that large to use deep learning models

For that use case, I suggest comparing Prophet against MSTL. MSTL decomposes seasonality and trends but can fit multiple seasonalities. It’s also faster than ARIMA. That’s good for your use case because with weekly data, you might find monthly patterns (last week of the month) as well as yearly patterns (last week of December)