I am trying to remember what we did when we moved to goemaxima.
One reasource you have, if you have been running STACK for some time, is the qtype_stack_cas_cache table in the database. That caches the command that was sent to Maxima, and the response that was recieved at the time.
Running through a few thousand rows of the table makes a good load test. I remember thinking about scripging that.
But, I don't think we ever did, because goemaxima was cearly faster than we had before (about 2x).
I think that, to prove that, all we did was to use Admin -> Plugins -> Question types -> STACK -> bulk test script on a course with a few hundred questions. Comparing the run-time of that script with our old setup and our new setup (remebering to clear the CAS cache inbetween) was sufficient testing for us.
(Note, that tests pretty-much single-threaded performance of goemaxima, not true capacity.)
One reasource you have, if you have been running STACK for some time, is the qtype_stack_cas_cache table in the database. That caches the command that was sent to Maxima, and the response that was recieved at the time.
Running through a few thousand rows of the table makes a good load test. I remember thinking about scripging that.
But, I don't think we ever did, because goemaxima was cearly faster than we had before (about 2x).
I think that, to prove that, all we did was to use Admin -> Plugins -> Question types -> STACK -> bulk test script on a course with a few hundred questions. Comparing the run-time of that script with our old setup and our new setup (remebering to clear the CAS cache inbetween) was sufficient testing for us.
(Note, that tests pretty-much single-threaded performance of goemaxima, not true capacity.)