by Andrea Bicciolo.
Hello Hugh,
it is possible to run a CLI cron on a separate machine "Server C" dedicated to this task, however you must ensure "Server A" and "Server C" share the same moodledata folder, points to the same database on "Server B" and runs exactly the very same Moodle codebase. And you should also be prepared to manage some administrative overhead when coming to Moodle updates.
Before going to the above route, you may want to evaluate the cost of upgrading to a better performing server against the cost of a more complex infrastructure. Maybe it is just a matter of adding more RAM. If you are running on a Linux box and running cron via CLI you could also invoke your cron using "nice", lowering the process priority,
it is possible to run a CLI cron on a separate machine "Server C" dedicated to this task, however you must ensure "Server A" and "Server C" share the same moodledata folder, points to the same database on "Server B" and runs exactly the very same Moodle codebase. And you should also be prepared to manage some administrative overhead when coming to Moodle updates.
Before going to the above route, you may want to evaluate the cost of upgrading to a better performing server against the cost of a more complex infrastructure. Maybe it is just a matter of adding more RAM. If you are running on a Linux box and running cron via CLI you could also invoke your cron using "nice", lowering the process priority,
