Papers › Sliced Recursive Transformer
Sliced Recursive Transformer
Zhiqiang Shen, Zechun Liu, Eric Xing
We present a neat yet effective recursive operation on vision transformers that can improve parameter utilization without involving additional parameters. This is achieved by sharing weights across the depth of transformer networks. The proposed method can obtain a substantial gain (~2%) simply using naive recursive operation, requires no special or sophisticated knowledge for designing principles of networks, and introduces minimal computational overhead to the training procedure. To reduce the additional computation caused by recursive operation while maintaining the superior accuracy, we propose an approximating method through multiple sliced group self-attentions across recursive layers which can reduce the cost consumption by 10~30% with minimal performance loss. We call our model Sliced Recursive Transformer (SReT), a novel and parameter-efficient vision transformer design that is compatible with a broad range of other designs for efficient ViT architectures. Our best model establishes significant improvement on ImageNet-1K over state-of-the-art methods while containing fewer parameters. The proposed weight sharing mechanism by sliced recursion structure allows us to build a transformer with more than 100 or even 1000 shared layers with ease while keeping a compact size (13~15M), to avoid optimization difficulties when the model is too large. The flexible scalability has shown great potential for scaling up models and constructing extremely deep vision transformers. Code is available at https://github.com/szq0214/SReT.
In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Image Classification | ImageNet | SReT-B (384 res, ImageNet-1K only) | Number of params | 71.2M | #286 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-B (384 res, ImageNet-1K only) | Top 1 Accuracy | 84.8% | #286 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-S (512 res, ImageNet-1K only) | GFLOPs | 42.8 | #326 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-S (512 res, ImageNet-1K only) | Number of params | 21.3M | #326 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-S (512 res, ImageNet-1K only) | Top 1 Accuracy | 84.3% | #326 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-S (384 res, ImageNet-1K only) | GFLOPs | 18.5 | #388 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-S (384 res, ImageNet-1K only) | Number of params | 21M | #388 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-S (384 res, ImageNet-1K only) | Top 1 Accuracy | 83.8% | #388 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-T | GFLOPs | 1.1 | #868 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-T | Number of params | 4.8M | #868 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-T | Top 1 Accuracy | 77.6% | #868 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-ExT | GFLOPs | 0.7 | #981 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-ExT | Number of params | 4M | #981 of 1060 | Archive leaderboard | report |
| Image Classification | ImageNet | SReT-ExT | Top 1 Accuracy | 74.0% | #981 of 1060 | Archive leaderboard | report |
Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.
Methods
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections