Magento 2 Cron Job – How to Set Up Cron Job in Windows

This code inserts the cron job into cron_schedule table:

$job_code='my_great_job_code';
/* */
$time = time(); // or time()+60 if you want...
$date = strftime('%Y-%m-%d %H:%M:00', $time);
/* */
$schedule = Mage::getModel('cron/schedule');
$schedule->setCreatedAt(strftime('%Y-%m-%d %H:%M:00', time()));
$schedule->setScheduledAt($date);
$schedule->setStatus(Mage_Cron_Model_Schedule::STATUS_PENDING);
$schedule->setJobCode($job_code);
$schedule->save();

You should not call/run cron.php directly but cron.sh via system cronjob/crontab instead.

I can recommend Fabrizios Blogpost for more information about the Magento cron:

cron.php vs. cron.sh

In Magento’s root folder there’s a cron.php file and a cron.sh file. Briefly explained cron.sh internally calls cron.php and takes care of not executing more than one process in parallel. That’s a good thing, right? Well, sometimes… If you have long running tasks (e.g. a product import implemented as a task), these tasks will prevent anything else from being executed until the task has finished. You might have some other important tasks that shouldn’t wait or be skipped just because another task is running. Check the “Missed if Not Run Within” setting to configure the maximum delay a task can have to still be executed.

On the other hand using cron.php will start a new process every time it’s being called which could easily result in performance problems or race conditions for tasks operating on the same data. This is why cron.php should not be called directly. Find out more about cron groups later in this blog post for a nice solution on how to handle this situation.

http://www.webguys.de/magento/tuerchen-08-magento-cron-demystified/