"Generate Commit Message" being VERY slow

I couldn’t upload a video (mp4) to this forum so he’s a screenshot.

Recently, I’m experiencing an extremely git commit generations (well over 1 minute). Few questions:

  • how does it work?
  • is this happening on the cloud?
  • could you potentially use a small LLM and fine-tune it, then run it locally? (if not already)

However, I’m not 100% sure if the issue is to do with server overload/a queue system. The questions above assume that.

To reproduce:

  1. Make some changes
  2. Click “Generate Commit Message”

Additional information

  • Operating system: Windows 11
  • Cursor version: 0.45

The issue doesn’t necessarily stop me from using the full editor, but I might re-consider using the feature until this problem is solved.

Edit: this issue was solved out of the blue for me

Are the commit files heavy?
Do you have same speed issue with another commit?
Maybe staging & pushing one by one to check

I’m not sure if the AI also looks at other files (which haven’t been changed) but assuming it only looks at the changed files:

It also takes very long. Min 30 seconds. I tried creating a new file with minimal content, staged it and geneared a commit message. Seeing similar slow speeds

I’ve also noticed slower commit message generation today.

1 Like

Update here: I’m seeing very fast generations now (up to 2 sec max). I’m curious to hear if the issue was solved for you too. Could you try again?

Still slow.

I think I figured out the root cause:

Slow requests. After buying more fast requests, generations were very fast. I just used them up now, and generations are really slow now.

If they used a more effecient model, they wouldn’t need to add a slow queue like this. Really hoping they’ll consider switching the default to a smaller model, perhaps fine-tuned on writing commit messages.

1 Like

I thought that message generation does not count as premium request and was supposed to be “unlimited”.

1 Like

It doesn’t seem like it for me