This is reported by Kyong from Foothill:

I had a question on a troublesome Samigo query.
This is probably the most prevalent query in our slow query log.

select assessment0_.PUBLISHEDASSESSMENTID as col_0_0_,
count(assessment0_.ASSESSMENTGRADINGID) as col_1_0_ from
SAM_ASSESSMENTGRADING_T assessment0_ where assessment0_.FORGRADE=1
group by assessment0_.PUBLISHEDASSESSMENTID;

It's issued once every time Assessments link is clicked as an instructor.

Is it taking submission counts for every published test?
I don't really know how the resulting rows are used but it's quite
heavy since we have 320,000+ rows in SAM_ASSESSMENTGRADING_T.