We had a client email us who was curious if changing the debug keys in his SCORMEngineSettings file would effect his
performance in a positive manner. Here are the keys that we discussed.
<!--Server side-->
<!--key="KeepAuditLog" value="True" />-->
<!--key="KeepDetailLog" value="True" />-->
<!--key="KeepSoapLog" value="True" />-->
<!--Client side (default settings for new packages)-->
<!--key="DebugControlAudit" value="True" />-->
<!--key="DebugControlDetailed" value="True" />-->
<!--key="DebugRteAudit" value="True" />-->
<!--key="DebugRteDetailed" value="True" />-->
<!--key="DebugSequencingAudit" value="True" />-->
<!--key="DebugSequencingDetailed" value="True" />-->
<!--key="DebugLookAheadAudit" value="True" />-->
<!--key="DebugLookAheadDetailed" value="False" />-->
<!--key="DebugIncludeTimestamps" value="True" />-->
<!--key="DebugLookAheadDetailed" value="False" />-->
<!--key="DebugIncludeTimestamps" value="True" />-->
The answer is that you might get a little more speed on the client side out of
changing these settings to false:
changing these settings to false:
<!--key="DebugSequencingDetailed" value="True" />-->
<!--key="DebugLookAheadAudit" value="True" />-->
<!--key="DebugLookAheadAudit" value="True" />-->
<!--key="DebugIncludeTimestamps" value="True" />-->
The rest add negligible overhead. We don't think these will do all that much except on courses with a lot of SCOs or complex
sequencing and navigation.
sequencing and navigation.
Thank you,
Joe