[samigo-team] Samigo performance--limits and solutions

[Jim Mezzanotte]

Thanks Bryan--I saw this mentioned in a previous post and it looks
like great work!  Also good to see it's already in production. Our
development team is taking a look, so hopefully we'll include it soon.

Best,
Jim

On Tue, Apr 9, 2013 at 2:19 PM, Bryan Holladay <holladay at longsight.com> wrote:
> https://jira.sakaiproject.org/browse/SAM-1695
>
> Subtask 2 & 3 are verified in production.  Subtask 1 is still waiting for
> David to reply about production statistics.
>
> 2 & 3 have shown a 2000% reduction in the number of DB calls
>
>
> On Tue, Apr 9, 2013 at 2:07 PM, Jim Mezzanotte <jmezzanotte at rsmart.com>
> wrote:
>>
>> Hi all,
>>
>> We're encountering Samigo performance issues with large (800+) course
>> sites, and specifically in cases where groups of students (up to 200)
>> are taking an assessment simultaneously in one physical location with
>> the Respondus lockdown browser. There's not a way to decrease this
>> concurrent usage, so I wanted to get feedback from others on your
>> experience with Samigo performance limits, and any steps you've taken
>> to maximize performance.
>>
>> I'm referring specifically to speed of navigation between
>> questions/parts for students, as well as speed of access for
>> instructors scoring an assessment. Another thing I'm trying to
>> determine is whether access time for concurrent usage changes
>> according to these parameters:
>>
>> a) usage distributed across the tool in multiple sites
>> b) usage for multiple assessments in a single site
>> c) usage for a single assessment in a single site
>>
>> Determining this poses a challenge with manual testing (I'm looking
>> into automated testing). But thanks in advance for sharing any
>> experiences/solutions/best practices.
>>
>> Best,
>> Jim Mezzanotte
>> rSmart
>> _______________________________________________
>> samigo-team mailing list
>> samigo-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/samigo-team
>
>