...
Dave Ormsbee (Deactivated) performed the exploratory work on this topic - those details are in this page: Discovery: Transitioning XBlock User State Away from CSM
Also, an initial CSM plan was put together here: https://docs.google.com/document/d/1FwPc9VnQKrXRjzAGDTbRlBnpwE9-KMELkvnOfyT-Was/edit
Call Catalog
Julia Eskew (Deactivated) documented all CSM calls in edx-platform on this page: Courseware StudentModule (CSM) Call Catalog
...
In the courseware_studentmodulehistory table, a new row is added for each update and insert to the courseware_studentmodule table which is for a CAPA problem. At the moment, it keeps the history forever. The table's data is used by the course team for support purposes. The data is viewable as a "submission history" button attached to the problem in the courseware. The table data has also been used for development purposes to diagnose bugs - and, on rare occasions, to correct state-corrupting issues in production.
DevOps Parallel Work
DevOps is a partner in this work. They've created an Epic under which their CSM work is tracked - it's here:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
edx.org CSM Requirements
Current
...
The relevant "courseware_" table queries can be seen on that page. Click through each query and peak throughputs can be seen. The peaks on June 2nd, 2015 (a day of heavy requests) can be seen in this New Relic note
Searching through recent New Relic data, the SELECT/INSERT/UPDATE peaks in this note were found:
https://rpm.newrelic.com/accounts/88178/notes/45884590
and were:
| Query | Rate (calls/min) | |
|---|---|---|
| select | 30K | |
| update | 4K | |
| insert | 4K) | Rate (call/sec) |
| SELECT (before progress optimization) | 43.6K | 727 |
| SELECT (after progress optimization) (9/15/15) | 11.6K | 193 |
| UPDATE (6/17/15) | 5.41K | 90 |
| INSERT (6/2/15) | 2.5K | 42 |
<Insert information on data size requirements>
...