Re: [RFC] Mitigating Sashiko-driven iteration noise on the main MPTCP list

[gang.yan@linux.dev]

> 
> Gang, you mentioned deploying Sashiko locally. Did you see anything like
> the same cost, and what were you running it against? If this turns out
> to be particular to a fixed-quota subscription, I would rather find that
> out than have people avoid running reviews locally over a cost that does
> not apply to them.
> 

Hi Shardul,

Thanks for your reply.

Sorry for the delayed reply; work has kept me busy lately so I haven’t had much
time to check emails. Please also excuse my English — I might have caused some
confusion earlier. I'm using the API key and noticed the cost.

I’d like to share my experience with an API-key Sashiko deployment, which may help
folks on this list use Sashiko at lower cost.

I run Sashiko using Minimax as the LLM. Minimax offers a monthly subscription plan
and is quite affordable. (I submitted a small PR to Sashiko to fix some issues
I encountered while using it.)

One observation: reviewing large patch series via the web interface can burn through
the 5-hour quota very quickly. In contrast, using `sashiko-cli` from the command line
seems to cut token consumption significantly, this is from my practical testing.

I also tried GLM, which is another fixed-quota subscription model and relatively
more expensive. While its quality is not as good as Gemini or Opus, it still works
well for local code iteration.

I’m still relatively new to working with AI tools. If you have any approaches to save tokens,
would you mind sharing them on this thread?

Thanks
Gang

> Thanks,
> Shardul
>