[Coscheduling] CalculateAssignedPods cost too much time

[KunWuLuan]

PodGroup manager will try every node and every pod in CalculateAssignedPods()

scheduler-plugins/pkg/coscheduling/core/core.go

Lines 246 to 264 in cd3e4fb

	// CalculateAssignedPods returns the number of pods that has been assigned nodes: assumed or bound.
	func (pgMgr *PodGroupManager) CalculateAssignedPods(podGroupName, namespace string) int {
	nodeInfos, err := pgMgr.snapshotSharedLister.NodeInfos().List()
	if err != nil {
	klog.ErrorS(err, "Cannot get nodeInfos from frameworkHandle")
	return 0
	}
	var count int
	for _, nodeInfo := range nodeInfos {
	for _, podInfo := range nodeInfo.Pods {
	pod := podInfo.Pod
	if util.GetPodGroupLabel(pod) == podGroupName && pod.Namespace == namespace && pod.Spec.NodeName != "" {
	count++
	}
	}
	}
	return count
	}

When there are 5k or more nodes and 50000+ pods in cluster, CalculateAssignedPods() will cost 30+ms.
We should cache the number of assigned pods to save time in scheduling cycle.

[KunWuLuan]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[KunWuLuan]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[KunWuLuan]

/remove-lifecycle stale