Back to AI News
arxiv

Investigating the effects of the patch size in Time Series Foundation Models

A new arXiv study systematically examines how patch size affects encoder-only and decoder-only time series foundation models trained on the same data and compute budget. Across 97 GIFT-Eval tasks, encoder-only models favor smaller patches, while decoder-only performance follows a U-shaped curve with an intermediate patch size being optimal. The preferred decoder patch size increases with forecasting horizon, and encoder-only models benefit from longer context up to 2048 tokens. The work provides practical guidance for choosing patch size and architecture based on forecasting horizon and deployment constraints.

AI Brief

Offers concrete, empirically grounded design rules for patch-based time series foundation models, directly useful for practitioners and researchers.

arXiv:2611.02750v1 Announce Type: cross Abstract: Patch size is a central design choice in patch-based time-series foundation models, controlling temporal resolution, sequence length, and computational cost. We study how this choice interacts with transformer architecture through a controlled comparison of encoder-only and decoder-only forecasting models trained with the same data mixture and optimization budget. Across 97 GIFT-Eval tasks, encoder-only models consistently benefit from smaller patches, whereas decoder-only performance follows a U-shaped trend, with an intermediate patch size performing best in aggregate. Dataset-level results further show that the preferred decoder patch size increases with the forecasting horizon. For encoder-only models, increasing context length improves performance across patch sizes, although the gains diminish beyond a context length of 2048. Finally, training-compute and CPU-latency Pareto analyses reveal complementary regimes: decoder-only models provide efficient low-cost alternatives, while encoder-only models attain the highest overall accuracy. These results show that the choice of patch size and architecture should be made depending on the forecasting horizon and deployment constraints.
Be the first to rate this article.

Comments & Questions (0)

Captcha
Please be respectful — let's keep the conversation friendly.

No comments yet

Be the first to comment!