---
title: "Comment by Ahmet Özel on \"I Trained an Open Decision Model on a Free GPU in 46 Minutes. On My Tests, It Beat Laya.\" | Hashnode"
description: "Putting the request after 7,000 tokens is a useful stress test, especially after training on 384-token inputs. I would vary its position next: beginning, middle"
url: "https://hashnode.com/posts/i-trained-an-open-decision-model-on-a-free-gpu-in-46-minutes-on-my-tests-it-beat-laya/6abe69f809b5a81c854b6d98/comment/6ac88f155e564172d8ba764f"
---

[Discussion](https://hashnode.com/posts/i-trained-an-open-decision-model-on-a-free-gpu-in-46-minutes-on-my-tests-it-beat-laya/6abe69f809b5a81c854b6d98)

Comment [I Trained an Open Decision Model on a Free GPU in 46 Minutes. On My Tests, It Beat Laya.](https://hashnode.com/posts/i-trained-an-open-decision-model-on-a-free-gpu-in-46-minutes-on-my-tests-it-beat-laya/6abe69f809b5a81c854b6d98)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Oct 9](https://hashnode.com/posts/i-trained-an-open-decision-model-on-a-free-gpu-in-46-minutes-on-my-tests-it-beat-laya/6abe69f809b5a81c854b6d98/comment/6ac88f155e564172d8ba764f)

Putting the request after 7,000 tokens is a useful stress test, especially after training on 384-token inputs. I would vary its position next: beginning, middle, and end of the same filler, while keeping the request and allowed options unchanged.

The current setup always makes the final support request the relevant one. A second test could include a plausible but irrelevant ticket near the end while the real request sits in the middle. That would separate long-input tolerance from a preference for the last task-like passage. Reporting the twenty requests as paired outcomes would make those position effects visible without treating small percentage changes as stable rankings.