CPU load when Prometheus is scraping metrics from F5 BIG-IP LTM

We are experiencing an issue where Prometheus is scraping metrics from F5 BIG-IP LTM, causing high CPU and memory utilization on the F5 device.

Initial step, we have adjusted the scraping interval to 1 minute, but the issue still.

Are there any recommended tuning options or best practices?