TRAX LRS performances can be improved with a few commands that you should run on your production server:
composer install --optimize-autoloader --no-dev php artisan config:cache php artisan route:cache
These commands must be run again after each application update.
php artisan config:cache command must be run again after each config change.
You should not cache your config and your routes on your development server. If you did it, you can remove the caches with:
php artisan config:clear php artisan route:clear
Some xAPI use cases may require a high level of writing performances. Think about a simulation writing hundreds of statements per second. If you are in such a situation, consider the following options.
If your priority is to optimize writing performances, you should consider using the basic configuration profile.
This profile will record only statements and activities, as required by the xAPI specification, without indexing data. So the LRS will record statements faster.
The xAPI specification requires that the LRS must extracts activities from the incoming statements,
and record or update them into the database, so they become available thru the
However, recording activity definitions may be useless if you don't need to use the
So if you don't care about breaking the xAPI conformance test, you can disable the activities recording.
This option will be ignored if you don't use the basic configuration profile because activities recording is needed to support the other configuration profiles.
The xAPI specification requires that all the incoming statements must be validated before being recorded into the LRS.
However, validating statements may be useless if your statements always come from the same conformant providers. So if you don't care about breaking the xAPI conformance test, you can disable the statements validation.
This option can be used with any configuration profile. It will speed-up the writing process and you will be able to validate the statements later with the following command:
php artisan statements:validate
Using Laravel queues brings a few benefits:
Check the Laravel queues page to go further.
Using the Redis cache brings a few benefits because getting data from the Redis cache:
Check the Redis cache page to go further.