| commit | 4de4d1652bbe79802f6bbef88eee391465326502 | |
| author | David Mudrák <david@moodle.com> | |
| Mon, 25 Mar 2019 11:57:31 +0000 (25 12:57 +0100) | ||
| committer | David Mudrák <david@moodle.com> | |
| Mon, 1 Apr 2019 12:23:06 +0000 (1 14:23 +0200) | ||
| tree | 8829d1f524816cf0a5acd20468fb0f154e91824b | treesnapshot (tar.gz zip) |
| parent | 0920f35ed902211cc0aab70f1ecc6978d532f28d | commitdiff |
MDL-61667 analytics: Don't autoenable models with time splitting defined
When the API had originally been designed, it was assumed that the
presence of the time splitting method implies no requirement for the
machine learning backend and that it is a sign of less performance
demanding models. So it seemed to be safe and useful to have such models
automatically enabled. That assumption did not prove to be valid. Most
of the time is spent calculating indicators that depend on log tables.
We realized it would be useful to be able to specify the default time
splitting method without the need to have such models auto-enabled.
When the API had originally been designed, it was assumed that the
presence of the time splitting method implies no requirement for the
machine learning backend and that it is a sign of less performance
demanding models. So it seemed to be safe and useful to have such models
automatically enabled. That assumption did not prove to be valid. Most
of the time is spent calculating indicators that depend on log tables.
We realized it would be useful to be able to specify the default time
splitting method without the need to have such models auto-enabled.
| analytics/classes/model.php | diffblobblamehistory | |
| analytics/tests/privacy_test.php | diffblobblamehistory |