Try below search for list of searches in particular period. I hope it will help you.
index=_audit action="search" search=* NOT user="splunk-system-user" | table host user search *
The Monitoring Console can show how many searches are running. Select "Scheduler Activity: Instance" from the search menu to see how many searches run at a time.
It difficult to say if 6 is a good number since we know nothing about your server environment. Considering the default value is 2, 6 seems a bit high. Keep in mind that each search not only uses a CPU on the search head, but also uses a CPU on every indexer.
If you're not seeing skipped searches and the load on your SH and indexers is tolerable then 6 may be OK. It's possible not running that many searches. The MC will tell you.
You should see messages in the logs or MC about why searches are being skipped. Usually, it's because there are too many searches running, but that shouldn't be your problem with 6 searches per CPU (although it could be). Make sure all of your searches have a Schedule Window set ("auto" or some non-zero value). Try to spread scheduled searches around the clock rather than have them run at the top of the hour.
It's also possible searches are skipped because the same search is still running. If that's the case, tune the search to improve performance or increase the schedule interval.