- Rating
- 3
- Confidence
- 3
- Informativeness
- 3
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper asks whether personalized LLMs need a separate adapter for every user and then conducts several prelimilary experiments. It proposes LINEUP, which combines shared low-rank factors using the user’s history and current query, then adapts an eight-dimensional code for each user. Experiments on LaMP and LongLaMP report better performance than the evaluated baselines with much less per-user parameter storage.
Critical strengths
-
Compelling perspective. Prior work has explored how to balance shared and user-specific LoRA components, but this paper offers a useful capacity-allocation perspective: what should be shared, conditionally composed, and adapted for each user.
-
Clear empirical motivation. The analyses in Section 3 provide a coherent motivation for the design in Section 4. Cross-user reuse motivates the shared factors, variation across users and queries motivates conditional composition, and transferable corrections from user history motivate the compact user code. These experiments do not constitute a formal derivation, but they provide reasonable support for the design choices.
Critical weaknesses
-
Reproducibility of the experimental results. Although the appendix provides some implementation details and the authors state that the code will be released after de-anonymization, code and a complete reproduction package are not currently available. Given that LINEUP reports the best mean result on every evaluated metric, it would be helpful to provide an anonymous implementation, exact data splits, and evaluation scripts so that these results can be independently verified during review.
-
Limited evidence of generality. My major concern is the breadth of the evaluation. The LongLaMP results in the appendix are welcome, but LaMP and LongLaMP belong to a closely related family of history-based text tasks. It remains unclear whether the proposed capacity-allocation strategy transfers to other personalization settings, such as evolving user preferences or multi-turn assistance. Evaluation on at least one benchmark outside this family would substantially strengthen the paper’s generality claim.
Questions for authors
Please see the weaknesses above for my main concerns. Overall, I enjoyed reading this paper and found its perspective interesting. As someone familiar with this area, I look forward to the public release of the code.