Alex Robinson

When I tried testing a large cluster (95 nodes) with a bit of load on it I already started seeing some bad behavior from gossip. Specifically I'd see a small...

Dumb example fix for the `tightenNetwork` performance issue: https://github.com/cockroachdb/cockroach/pull/88472

Looking at it a bit more, `visitInfos` is also burning a bunch of CPU. There are a couple issues there: * We store all infos in a single map regardless...

I suppose that given that they're never re-gossiped once the nodes are removed, something like the new `crdb_internal.unsafe_clear_gossip_info("gossip-key")` function from #85013 could be used to manually clear out the old...

@kvoli @nvanbenschoten I'm also up for helping with a change that meaningfully changes the frequency of gossiping "gossip-clients" keys given that all they're used for is the periodic logging of...

> Changing the frequency of gossip-clients appears strictly beneficial. A cluster setting sounds good. Which sounds good - a cluster setting to change the frequency or to stop gossiping it...

It's fine if you aren't interested in a patch at the moment, but I thought I'd share some data from having completely ripped out the "gossip-clients" keys just to give...

> I think it would be great to patch in. Sorry for not being totally sure what you mean, but by "it" do you mean a complete rip out like...

> The release note isn't needed for this change because it doesn't require documentation changes. Does that mean you'd like me to remove it from the commit?

Sorry @omarkhairy21 , there have been no changes in our (lack of) support for queues in `wrangler dev --remote`.