- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes a training-free approach, Faster3D, to improve the image-to-3D models. It employs temporal token decoupling (TTD) to selectively reuse token velocities and cached-content restoration (CCR) to preserve cached attention keys/values. The reported speedups in the target structure or geometry sampling stage vary from 1.30x to 1.95x for five backbones.
Critical strengths
- Tokens associated with empty space may need fewer velocity evaluations while still providing useful attention context. This distinction is compelling.
- Reusing kv at their original positions and periodically refreshing all tokens forms a plausible practical system.
- Results across five backbones make this more convincing than a single-model optimization, although each backbone requires separate calibration.
Critical weaknesses
- Calibration needs clarification. Dataset separation, threshold construction, calib cost, and generalization are insufficiently specified.
- Reported speedups cover only the targeted sampling stage, while end-to-end pipeline latency, stage-level timings, and additional cache memory would make the practical gain easier to assess.
- In tab.1, the gains over Faster3DCache are fairly modest. eg. on TRELLIS, it achieves almost the same speedup and small improvements, w/o a overhead discussion. It's hard to judge the proposed method.
Questions for authors
- Does calibration use any evaluation objects or closely related assets?
- How accurately does activity predict velocity-reuse error across timesteps and backbones?
- Does CCR outperform spending the same runtime on additional fresh token evaluations?
- How much of refresh’s benefit comes from fresh velocities versus fresh K/V?
- What are the end-to-end latency, memory overhead, and worst failure cases?
2 comments
Thank you again for your time and thoughtful feedback. With two days remaining in the discussion period, please let us know if any questions or concerns remain after our responses. We would be happy to provide further clarification.
Thanks for your positive feedback that our paper identifies a compelling distinction, that we provide convincing evidence, and that our method Faster3D forms a plausible practical system across diverse backbones. Below we respond to each of your concerns.
Q1&W1: In Appendix B.1, we clarify that all calibration sets are disjoint from Toys4K-210 and that configurations are fixed before testing. Table 5 in Appendix B.3 reports the calibration data source, sample count, and threshold construction for each backbone. As shown in the table below, we test two different calibration images randomly sampled from the disjoint Toys-4k and 3D Arena datasets. The main metrics suggest that Faster3D generalizes across calibration sets.
Q5&W2: The 3D asset generation models generally consist of geometry generation and texture generation stages, thus requiring different acceleration techniques due to the architectural differences. We also argue that the geometry generation is building a strong and important basis for the texture generation stage. There are also numerous 3D models such as Hi3DGen and TripoSG that focus solely on geometry generation, while existing acceleration method Fast3Dcache focuses on geometry synthesis. Our Faster3D follows the same scope of Fast3Dcache, and all reported speedups refer specifically to geometry sampling.
Below, we report the end-to-end geometry generation speedups and GPU memory as you mentioned. Our method Faster3D achieves large ratios of speedups at the cost of necessary increased memory usage.
Regarding failure cases, we did not observe severe visual degradation relative to the full-compute baseline. Nevertheless, velocity reuse remains an approximation and does not guarantee identical geometric outputs. Figures 1, 7, and 12–16 provide numerous qualitative comparisons across different backbones for your reference.
W3: First, the improvements of geometry generation are not always well reflected in metrics. Fast3Dcache loses substantial geometric detail at a sampling speed comparable to our method. By comparison, Faster3D more closely preserves the completeness of geometric structures and fine-grained details. Please refer to the Fig.1, Fig.7 and Fig.12-16 for comparisons. Also, noticeable metric improvements and robustness to diverse backbones can be observed on vIoU, Ulip-2 and Uni3D in Table 1.
Q2: As the table below, we compute the velocity-reuse MSE of Faster3D and Fast3Dcache on TRELLIS with Toys4K-210 as the dataset. These suggest that activity-prediction velocity-reuse could more accurately approximate the velocities of the selected tokens. More results are reported in the additional Appendix C.6.
Q3: To study the importance of CCR mechanism, we disable the CCR and only apply the TTD technique. This operation allows for additional fresh token computations while degrading the performance, as demonstrated below with lower vIoU, CD and F-score metrics.
Q4: To test the benefit of refresh, we compare refreshing only velocities, only K/V, both, or neither, with token masks and refresh steps fixed on 210 Toys4k objects. As shown below, refreshing K/V alone provides a larger gain than refreshing velocities alone. Both components are beneficial, and refreshing both achieves the best metrics performance.