- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 3
Read review
Paper summary
To address challenges in scaling multimodal large models—such as fragmented computing resources, hardware heterogeneity, and the reliance of traditional distributed training on centralized management and high-bandwidth communication—the authors propose TiS, an API-based computation-sharing framework. TiS decouples local multimodal adaptation from the computation performed by the frozen remote large model; it retains raw data, trainable modules, and optimizers locally, transmits embeddings and labels to the remote end, and updates the adapter using the returned input gradients. Through dynamic scheduling, the framework assigns training requests to independent service nodes hosting the same model, enabling diverse hardware to participate collaboratively in training while supporting both standard inference and gradient computation. In my view, this work offers a practical solution for leveraging distributed computing resources to scale multimodal models—characterized by clear computational boundaries and a service-oriented design—and demonstrates robust multi-node scalability.
Critical strengths
- The author proposes a scheme for sharing computing resources via service interfaces, designed to address complex conditions characterized by independent management, hardware heterogeneity, and limited network bandwidth; this approach holds practical value for deployment.
2.The authors provide large-scale validation and demonstrate near-linear throughput scaling across four nodes with a fixed global batch size.
Critical weaknesses
-
TiS bears a strong resemblance to existing architectures for split learning, remote automatic differentiation systems, and multimodal federated large models (such as Uniflow and FedNano); the authors failed to adequately distinguish their work from these existing approaches in the "Related Work" section.
-
Although the authors conducted experiments with large-scale models, there is a significant lack of experiments regarding module ablation and parameter validation.
Questions for authors
The author has not considered complex operational scenarios—such as node departures, retry mechanisms, protection for low-resource languages, and data locality. Overall, while the author's idea is promising, the experimental analysis fails to substantiate the claims; I will lower the score if the author does not address my questions.
3 comments
[Q1] The author has not considered complex operational scenarios—such as node departures, retry mechanisms, protection for low-resource languages, and data locality. Overall, while the author's idea is promising, the experimental analysis fails to substantiate the claims; I will lower the score if the author does not address my questions.
We thank the reviewer for this suggestion. TiS originated as a training framework, so the initial draft emphasized model quality and did not clearly define which system properties should be measured or how far system validation should go. The 70-language run shows that the framework can carry a real-scale training job, but it is not itself a system validation of TiS. The reviewer's comment helped us clarify this. The revision adds 8–9 pages and dedicates Figures 4–5 to system throughput, heterogeneous pooling, elasticity, communication cost, and ablation, reporting system validation separately from model quality.
- Node departure and retry. Elasticity and failure recovery share one liveness rule: at step boundaries the scheduler probes whether a worker is online and estimates its throughput, then adds or removes members and re-dispatches samples. Elasticity is measured in Fig. 5(a): the pool grows from 8 to 12 and shrinks to 4, holding at 35.7, 46.2, and 20.4 samples/s; each membership change requires no restart of the training process. Failure re-dispatch uses the same check: timed-out samples return to the queue by sample ID.
- Low-resource languages.
- Finding. The appendix is renamed Detailed Results. §4.1 now analyzes the low-resource sources: only five source languages (Burmese, Khmer, Assamese, Amharic, Georgian) trail the best baseline by more than 5 COMET, while the reverse directions are normal (English→Burmese 89.1 vs 87.2 for Gemini, English→Khmer 83.1 vs 81.4). The gap is therefore on the input side, not in target decoding.
- Cause. The source of the gap is the frozen Whisper encoder on the input side. These five languages are underrepresented in Whisper's pretraining data, so the encoder has not learned features that separate their phonemes and acoustic cues. With the encoder frozen, the adapter can only adapt on top of this fixed acoustic representation and cannot compensate for the missing coverage.
- Unfreezing the encoder. We also tested unfreezing the encoder (636.97M), and it brings no clear quality gain: held-out ASR and S2TT quality shows no material change, while step time rises substantially, so the revision keeps the encoder frozen. Encoder capacity is therefore not the binding constraint.
- Release. The full 70×69 per-direction results will be released with the code.
- Data locality. Raw audio, trainable parameters, and optimizer state stay at the edge; the service receives only embeddings and label token IDs.
Thank you for your response. I have seen your revisions; I am maintaining my score, as I feel that 3/2 is sufficient.
We thank the reviewer for pressing on this point. The review describes the data path—embeddings out, input gradients back—but the data path is the interface, not the contribution. The paper's claim concerns what the service side is allowed to be.
Classical split learning places the server inside the training system: the server holds trainable parameters, runs a training process for the duration of the job, and its parallelism is fixed when the job starts.
TiS makes a different assumption: the edge and service sides are administratively isolated, the training party needs no SSH access or server control, and the two sides interact only through the API. The process resident on the service side is an inference process, and it holds no training state between steps. A TiS worker is an inference worker plus a gradient-return path, serving standard inference and training-gradient-return requests from the same resident checkpoint. This changes the deployment unit from "a training rank" to "an interchangeable worker."
This is the difference the paper measures. The following are the ways TiS differs from split learning:
For FedNano and UniFL specifically:
TiS is therefore a pool of independently managed inference services rather than a federation of training clients.
Thank you for the comment. The revision adds the following ablations and system measurements: