in our current environment nodes only exist when a job is requesting them, and go away when the job is done. So an actual qmgr create node command is run when it starts up and a qmgr delete node happens when the job is gone.
The create node call is (in computer terms) slow, a bottle neck level slow.
(in human terms its ~0.4 seconds)
the alternative is to pre create 250K+ nodes once when the facility is created and then call a set node to update info on the node instead of a create node command when a job is submitted.
so my question here is in 2 parts,
does having 250K nodes that are mostly down/offline slow down the PBS server or scheduler to any noticeable extent?
does anyone suspect that a qmgr set node command will happen significantly faster than a create node command?