[Building Sakai] Heavy Samigo query

[Kusnetz, Jeremy]

One of the queries that we see piling up during high load is the
following (this is from innotop).  We heavily utilize Samigo, with
thousands of active classrooms, many with a dozen or more assessments.
This is on CLE 2.6.3

 

EXPLAIN 

select publishede0_.ASSESSMENTID as col_0_0_, publishede0_.SCORINGTYPE
as col_1_0_, publisheda1_.SUBMISSIONSALLOWED as col_2_0_ from
SAM_PUBLISHEDEVALUATION_T publishede0_, SAM_PUBLISHEDACCESSCONTROL_T
publisheda1_ where publishede0_.ASSESSMENTID=publisheda1_.ASSESSMENTID

_____________ Sub-Part 1 ______________  __________________ Sub-Part 1
__________________

Select Type: SIMPLE                      Select Type: SIMPLE


      Table: publishede0_                      Table: publisheda1_


 Partitions:                              Partitions:


       Type: ALL                                Type: eq_ref


 Poss. Keys: PRIMARY,FK94CB245F9482C945   Poss. Keys:
PRIMARY,FK2EDF39E09482C945         

      Index:                                   Index: PRIMARY


 Key Length:                              Key Length: 8


  Index Ref:                               Index Ref:
sakai_300.publishede0_.ASSESSMENTID

  Row Count: 45874                         Row Count: 1


    Special:                                 Special:


 

Press e to explain, f for full query, o for optimized query

 

Jeremy Kusnetz | Sr. Systems Engineer

 

American Public University System 
American Military University  |  American Public University
661 S George Street, Charles Town, WV 25414 
T 304-885-5333 | M 703-967-5212 |  jkusnetz at apus.edu
<mailto:jkusnetz at apus.edu> | www.apus.edu <http://www.apus.edu> 

 

This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20111012/a5182338/attachment.html