Pool with NTS

[Hal Murray]

Richard Laager said:
> On 2026-03-23 00:33, Hal Murray via devel wrote:
>> [Someplace, there is code that counts servers that also
>> counts the pool slots.  They should be skipped.  I think
>> we should fix this even though it is a user-visible change.]

> Yes, please. This is a pet annoyance of mine. :)

Mine too.  Thanks for the encouragement.

I just pushed a fix.

---


>> That lets you get all 4 cloudflare servers.

> If you want multiple CloudFlare servers that all have the same name,
> isn't that what "pool" is for? (Of course, you have pointed out problems
> with the "pool" implementation.) 

Yes and no.  There are big pools and little pools.

For little pools, like CloudFlare, it should grab them all and stop.

For big pools, it grabs some and prunes some, dancing around minclock, and 
maxclock and servers that fade out.

The current code assumes all pools are big.  We could add a keyword like 
"all" to mark a pool slot as small.

After I push the fix for NTS and pools, you can play with minclock and 
maxclock.  I think if you set them just right, it might do what I think a 
small pool should do.  (Or you can play with it now as long as you don't 
use NTS.)

-------

There is another option we might want for small pools.  Rather than use 
all of them, pick the best N.  The idea is to get several from one vendor 
and several others from another vendor so you don't put all your eggs in 
one backet.

Currently the maxclock logic assumes all pools are part of the same pool.  
We'd have to add a bunch of per-pool logic.




-- 
These are my opinions.  I hate spam.