FYI, there is already a 'wait' stanza, unfortunately, that's not good enough.

error we got

fatal: unable to access 'https://github.com/stevearc/oil.nvim.git/': Failed to connect to github.com port 443 after 19477 ms: Couldn't connect to server

This typically means we've burst too much :(

Unfortunately, even if with checker.concurrency = 1, since each check is really fast, the overall speed is still too fast and bursty.

The second concurrency option exists. It may work.

I already have

require('lazy').setup('plugins',
  { concurrency = 1, checker = { enabled = true, concurrency = 1, frequency = 2 * 86400, wait = true }, })

still too fast once checker is in working

Oh..

I'll see to add something for this this evening

I have a similar issue. In my case, I use HDD for disk and have limited network bandwidth.
It would be nice to have an option to select the previous behavior.

@mimikun what do you mean with previous behavior?

Before this commit: 0614ca6

After this commit, my plugin update speed, which was set to concurrency = 1, became incredibly slow (I've now tweaked it a bit and it's gotten a bit better. about: https://github.com/mimikun/dotfiles/blob/f64ba2b10333a65bc06e76aeefbb15f8ecdcdc99/dot_config/nvim/lua/core/lazyvim.lua#L4-L17).

I don't mean to pile on because this might certainly not be in scope for this plugin, but my corporate VPN too seems to be blocking :Lazy update.

I have the settings suggested above:

require("lazy").setup({
  concurrency = 1,
  checker = { enabled = true, concurrency = 1, frequency = 2 * 86400, wait = true },
  ...
})

The first few fetchs work fine and then once something fails it continues to fail. I checked with IT and they said the system was flagging these requests as suspicious.

If I'm off my company VPN it works fine so this isn't a deal breaker for me personally, just an annoyance.

Thank you folke! Life saving for us programming inside controlled environments, now I can have a way to tweak to the near allowed capacity and not got banded by our network policy!

One thing to point out, my previous config was like this

require("lazy").setup({
  concurrency = 1,
  checker = { enabled = true, concurrency = 1, frequency = 2 * 86400, wait = true },
  ...
})

The concurrency = 1 on the top-level needs to be taken out or it does not seem to honor the throttle. The concurrency = 1 inside checker seems fine, leaving out there still seem to honor the throttle.

Thank you again!!