osquery-perf fails with fatal error: concurrent map read and map write

[getvictor]

Fleet version:
4.60.0
Web browser and operating system:

---

💥  Actual behavior

In loadtest, after enrolling 60k MDM hosts, I'm occasionally seeing osquery-perf containers die and restart.
From the logs for a stopped container, I see:

The full loadtest doc is at https://docs.google.com/document/d/1HafECokrZ3jnzRskxMtJwp4k1E2uBTbO9vfKEUtyykI

🧑‍💻  Steps to reproduce

1. See loadtest doc.

🕯️ More info (optional)

The message points at this line in agent.go:

			if existingEntry, ok := a.scheduledQueryData[scheduledQueryName]; ok {

I recommend using sync.Map for scheduledQueryData struct member.