Scheduled tasks (cron) in Deno - Performance & Optimization

Performance: Scheduled tasks (cron)

MEDIUM IMPACT

Scheduled tasks affect background CPU usage and can impact server responsiveness and resource availability.

Running periodic background tasks without blocking main server operations

Deno

import { cron } from "https://deno.land/x/croner@6.0.5/mod.ts";

cron("*/1 * * * *", async () => {
  await heavyAsyncTask();
});

async function heavyAsyncTask() {
  // simulate async work
  await new Promise(resolve => setTimeout(resolve, 100));
}

Runs tasks asynchronously without blocking event loop, allowing server to stay responsive.

📈 Performance GainNon-blocking execution reduces CPU spikes and keeps event loop free.

Running periodic background tasks without blocking main server operations

Deno

setInterval(() => {
  // heavy synchronous task
  for (let i = 0; i < 1e9; i++) {}
}, 1000);

Blocks the event loop causing delayed responses and high CPU usage.

📉 Performance CostBlocks event loop for hundreds of milliseconds every second, causing poor responsiveness.

Performance Comparison

Pattern	CPU Usage	Event Loop Blocking	Responsiveness Impact	Verdict
Synchronous heavy task in setInterval	High CPU spikes	Blocks event loop for 100+ ms	Delays server responses	[X] Bad
Asynchronous cron task with lightweight work	Moderate CPU usage	No event loop blocking	Maintains server responsiveness	[OK] Good

Rendering Pipeline

Scheduled tasks run outside the rendering pipeline but can affect server responsiveness and resource availability, indirectly impacting user experience.

→Event Loop

→CPU Usage

⚠️ BottleneckBlocking synchronous tasks cause event loop delays.

Optimization Tips

1Avoid heavy synchronous code inside scheduled tasks to prevent event loop blocking.

2Use asynchronous APIs and cron libraries to run tasks without blocking.

3Monitor CPU usage and event loop delays to detect scheduling performance issues.

Performance Quiz - 3 Questions

What is the main performance risk of running heavy synchronous code inside a scheduled task in Deno?

A It reduces memory usage.

B It increases network latency.

C It blocks the event loop causing delayed responses.

D It improves CPU efficiency.

DevTools: Performance

How to check: Record a CPU profile while scheduled tasks run; look for long tasks blocking the event loop.

What to look for: Long blocking tasks or CPU spikes indicate poor scheduling; smooth CPU usage indicates good practice.

Practice

1. What is the main purpose of using scheduled tasks (cron) in Deno?

easy

A. To compile Deno scripts faster

B. To manually trigger functions on user input

C. To debug code step-by-step

D. To run code automatically at specific times or intervals

Solution

1. Step 1: Understand scheduled tasks

   Scheduled tasks run code automatically without manual intervention.

2. Step 2: Identify cron job purpose in Deno

   Deno's cron jobs automate running code at set times or intervals.

3. Final Answer:

   To run code automatically at specific times or intervals -> Option D

4. Quick Check:

   Scheduled tasks = automatic timed code run [OK]

Hint: Scheduled tasks run code on a timer, not manually [OK]

Common Mistakes:

• Confusing scheduled tasks with manual triggers
• Thinking cron is for debugging
• Assuming cron speeds up compilation

2. Which of the following is the correct way to import the croner library in a Deno script?

easy

A. import Cron from "croner";

B. require('croner');

C. import { Cron } from "https://deno.land/x/croner@6.0.0/mod.ts";

D. import * as Cron from 'cron';

Solution

1. Step 1: Check Deno import style

   Deno uses ES module imports with URLs, not CommonJS require.

2. Step 2: Identify correct croner import

   The official croner import uses a URL with version and named import.

3. Final Answer:

   import { Cron } from "https://deno.land/x/croner@6.0.0/mod.ts"; -> Option C

4. Quick Check:

   Deno imports use URLs and named imports [OK]

Hint: Deno imports use full URLs, not short names or require [OK]

Common Mistakes:

• Using require() which is Node.js style
• Importing from 'cron' instead of 'croner'
• Using wildcard import without URL

3. What will the following Deno croner code output when run?

import { Cron } from "https://deno.land/x/croner@6.0.0/mod.ts";
const cron = new Cron("* * * * *", () => {
  console.log("Hello every minute");
});
cron.start();

medium

A. Prints "Hello every minute" every second

B. Prints "Hello every minute" every minute

C. Prints "Hello every minute" once immediately

D. Throws a syntax error

Solution

1. Step 1: Understand the cron pattern "* * * * *"

   This pattern means the task runs every minute.

2. Step 2: Analyze the callback behavior

   The callback logs "Hello every minute" each time the cron triggers.

3. Final Answer:

   Prints "Hello every minute" every minute -> Option B

4. Quick Check:

   Cron pattern "* * * * *" = every minute [OK]

Hint: Five stars in cron means every minute [OK]

Common Mistakes:

• Thinking it runs every second
• Expecting immediate output without waiting
• Confusing cron syntax with other formats

4. Identify the error in this Deno croner code snippet:

import { Cron } from "https://deno.land/x/croner@6.0.0/mod.ts";
const cron = new Cron("60 * * * *", () => {
  console.log("This runs every hour");
});
cron.start();

medium

A. The cron pattern "60 * * * *" is invalid because minutes must be 0-59

B. Missing await before cron.start()

C. Callback function should be async

D. Cron library does not support hourly tasks

Solution

1. Step 1: Check the cron pattern validity

   Minutes field must be between 0 and 59; "60" is invalid.

2. Step 2: Confirm other code parts

   cron.start() does not require await; callback can be sync; hourly tasks are supported.

3. Final Answer:

   The cron pattern "60 * * * *" is invalid because minutes must be 0-59 -> Option A

4. Quick Check:

   Minutes range = 0-59, 60 is invalid [OK]

Hint: Minutes in cron must be 0-59, not 60 or above [OK]

Common Mistakes:

• Using invalid minute value 60
• Thinking cron.start() needs await
• Assuming callback must be async

5. You want to schedule a Deno task to run every weekday at 9:30 AM using croner. Which cron pattern is correct?

hard

A. 30 9 * * 1-5

B. 9 30 * * 1-5

C. 30 9 * * 6,7

D. 0 9 * * 1-5

Solution

1. Step 1: Understand cron fields order

   Cron fields are: minute, hour, day of month, month, day of week.

2. Step 2: Match 9:30 AM on weekdays

   Minute = 30, hour = 9, day of week = 1-5 (Monday to Friday).

3. Final Answer:

   "30 9 * * 1-5" -> Option A

4. Quick Check:

   Minute=30, Hour=9, Weekdays=1-5 [OK]

Hint: Minute first, hour second, weekdays 1-5 for Mon-Fri [OK]

Common Mistakes:

• Swapping hour and minute fields
• Using weekend days 6,7 instead of weekdays
• Setting minute or hour to zero incorrectly