- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper starts from the claim in its title: the low- and high-frequency parts of a workload spectrum have different structure and should not be handled by the same operator. DuoFreq implements this by linearly extrapolating the lookback into the horizon, taking an rFFT over the concatenation of history and extrapolation, and then applying a smooth identity-centred real gain to the low band (SLFM) and local/global gains plus complex linear blocks to the high band (LG-HFM, CST). Experiments use five cloud traces, eleven baselines and four horizons, plus ablations and an efficiency study; the model has about 0.61M parameters and reports the best MSE in 17 of 20 settings.
Critical strengths
- Well written. The motivation, the two-band design and the figures are easy to follow, and the paper reads cleanly from start to finish.
- Targets a real problem and stays lightweight. Cloud workload forecasting underpins auto-scaling and resource provisioning, and at 0.6M parameters the model is small enough to be deployed per service.
Critical weaknesses
- The transfer results are hard to accept as they stand. RQ3 evaluates on variables that were not used in training, so it should not come out easier than RQ1, which trains and tests on the same variables. Yet the unseen-half error is lower on four of five datasets (Huawei Memory 0.7068 vs 1.1057; Huawei CPU 0.4964 vs 0.6269; FaaS 0.1968 vs 0.2120; PaaS 0.0458 vs 0.0589). That direction is not explained.
- The role of SLFM needs stronger support. Removing it costs only 0.2–0.7% MAE, the smallest drop among the three proposed modules on four of five datasets. So a dedicated low-frequency module does not clearly help.
Questions for authors
- Unify the setting for the seen and unseen variables, especially the normalisation. Then explain why the seen numbers come out worse than the unseen ones.
- Give stronger support for the role and significance of SLFM.
Thank you for pointing out the difference between the reported RQ1 and RQ3 errors and for asking us to clarify the role of SLFM. We have expanded the transfer evaluation and added two structural comparisons and a zero-cutoff experiment.
1. Why the reported error on unseen variables can be lower
RQ1 reports the average error over all variables in each dataset. The original RQ3 experiment reports the average only over the held-out second half. Workload variables differ in their scales and patterns of variation. Both evaluations use the same per-variable standardization rule, so differences in raw scale are accounted for. However, standardized forecast errors can still vary considerably across variables. A lower error averaged over the held-out subset can therefore arise from which variables enter the average and does not imply that forecasting unseen variables is easier.
For each variable, we compute the standardization statistics from the first 70% of its timeline. In RQ3, the historical observations of the target variables are used only for standardization. Model training, validation, and checkpoint selection use source variables only.
The revised Table 4 averages results across the original partition and two additional random partitions, shared by all nine models. On FaaS, the transfer MSE changes from 0.1968 under the original partition to 0.2127 after averaging across the three partitions, close to the RQ1 value of 0.2120. On PaaS, it changes from 0.0458 to 0.0590, close to the RQ1 value of 0.0589. These results show that the gap between the two reported errors depends on the choice of target variables.
2. What SLFM contributes
The SLFM ablation bypasses the gain predictor and removes the smoothness penalty. The low-frequency coefficients enter reconstruction unchanged, so the comparison isolates the benefit of learning to refine them. The improvement is clearest on Huawei Memory, where removing SLFM raises the horizon-averaged MSE from 1.1057 to 1.1283 and MAE from 0.5481 to 0.5521. On Huawei CPU, the average MSE rises from 0.6269 to 0.6336.
The two new structural comparisons test how the bands should be processed. Symmetric-HFM-CST retains the band split and applies the high-frequency pipeline separately to both bands. FullSpectrum-HFM-CST applies the same pipeline to the entire spectrum. On Huawei CPU, their horizon-averaged MSEs are 0.6650 and 0.6497, respectively, compared with 0.6269 for DuoFreq. The symmetric comparison is particularly relevant here because both designs retain the two bands and differ in how they process the low band.
We also added a zero-cutoff setting that keeps DC protection and removes the separate low-frequency band. On Huawei CPU at a forecast horizon of 288 steps, all tested settings that assign a low-frequency band to SLFM achieve lower validation and test MSE than the zero-cutoff setting. Together, these results support refining the retained low-frequency coefficients with smooth residual gains and giving the two bands different transformations.