- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This work investigates WindowLoRA: LoRA that can only observe a subset of the past context. Another way to view this method is attention dropout, where at each step, a random collection of positions in the context is forced to have zero attention. This method was inspired by the failure of models to retain their pretraining capabilities. By changing the available window for fine-tuning, WindowLoRA provides a controlled mechanism to compare behavior using the full context or only a subset. This work describes a small synthetic task, acting as a clean testbed for comparing different possibilities of forgetting. Experiments on this synthetic task reveal a trade-off between retention and adaptation, where greater amounts of constraints lead to better retention but worse adaptation. WindowLoRA is then tested on real models on natural datasets, again showing a trade-off between this method and others.
Critical strengths
This work provides both a view of why retention fails and a method that can interpolate between failing to retain and retaining. WindowLoRA is thus a strong avenue for experimenting with the failures of retention and a fine-tuning module that provides better control of retention. Additionally, this method could be used similarly to dropout in MLPs, where increasing the dropout fraction leads to more stable training and possibly less overwriting of pretrained behaviors.
Critical weaknesses
The paper's structure has been a bit challenging to follow. The related work is in the middle of the paper, breaking up the method definition and the experiments. The experiment definitions and results are in different sections, without this structure being described at the beginning of Section 5. It took a handful of rereads to realize Section 5.3's results are in Section 6.3.
A core element of WindowLoRA is that it provides a window into what is causing poor post-training performance: conflicting prompts or disjoint support. Figure 2 shows an example of each. However, the only main difference between the methods is the replay result on the last one (this was also hard to identify on the first few reads). This separation can only be seen if there is pre-training data that can be replayed, not in the common setting with frontier models where the pre-training data corpus and data weighting is unknown.
Questions for authors
- What precisely is the task used in Table 1? How are the 4 labels selected? The main body is light on details about how this task is created, and references to the appendix were not enlightening, nor was an anonymized codebase linked. The structure of this task could be quite enlightening regarding the results. Label generation being random or structured creates considerably different tasks.
- Figure 1 shows that the sampled locations are evenly spaced. Just to confirm, is this a stylistic choice for the figure? My understanding is that these positions are sampled randomly.
- Are there experiments testing whether real data shows disjoint support to the target task or not? This seems to be a key point in the development of WindowLoRA, but it is only shown to hold in synthetic settings. We don't have the exact training data for these models, but replaying some of WikiText along with the task should work similarly to the synthetic setting.
Minor Issues: Line 80: Quote formats look better with `` and ‘‘. Line 98: method -> methods. Line 240: figure -> Figure.
9 comments
W1: The paper's structure has been a bit challenging to follow concern
We will reorganize in the camera-ready version. Few things we will do:
- The related works section after section 1 as this is more standard. Alternatively we might move this section into a section before the conclusion
- The experiments definition and setting can be merged into one section (ie. merge section 5 and section 6)
W2: A core element of WindowLoRA is that it provides a window into what is causing poor post-training performance
First of all, indeed that one fundamental difference is that replay assumes that pretraining data accessible either fully or partially which in many of cases is not feasible in LLMs training and we don't assume such assumption for the WindowLoRA. Another difference is that our family framework also enables us to control the retention strength, unlike replay where thing could be harder to implement.
We thank for the to highlight the motivation and states that WindowLoRA is controllable framework to study retention-adaptation tradeoff and also raising interesting connection between this and DropOut method in MLPs. We address the weaknesses and questions in the following sections.