This article is provided to help explain how memory operates in your Learnosity sessions, and why some sessions may appear to be smaller than others, but could actually cause a memory related error.

When calling the Data API, there are numerous types of API calls that can lead to "out of memory" issues. When you encounter an out of memory issue, you’ll receive an error stating ‘Response size too large’ (HTTP error code 400, and Learnosity error code 20027).

While there is guidance on the limit of sessions the Data API can handle, this is not a hard and fast rule. For example, our guidance on the maximum number of students in some of our reports is 100. However, the number of students a report can handle will also be determined by session size. As you can see on our reference site, sessions include other elements (endpoints) such as responses, scores, metadata and more.

Examples of things that can increase the size of a session:

• Excessive number of Items
• Large size of Items in the session
• Excessive use of features on an item
• Base64 encoding schemes (poor data density)

Sessions can also contain data from you, the customer, and this can also influence the total session size. If there are additional objects contained in the request that you send, this is likely to add to the overall session size. 

Therefore, one request from you can be smaller in terms of the number of sessions, but larger in total size (due to the differing constituent components inside those sessions). So back to the Reporting example, a request containing 65 students may cause an out of memory issue, while another request containing 100 students may work without a problem. 

For any queries or more information on this topic, please contact our Customer Support team.