How to Optimize Medusa Performance on Your Seedbox for Maximum Download Speeds

If you've been running Medusa on your seedbox for a while, you've probably noticed it can get a little sluggish over time — especially once your show library grows past a few dozen series. Slow post-processing, delayed backlog searches, and a database that keeps ballooning in size are all signs that your setup needs some tuning.

The good news is that Medusa is surprisingly configurable once you know where to look. In this guide, you'll learn practical techniques to keep Medusa running lean and responsive on your SonicBit seedbox: from database maintenance and scheduler adjustments to post-processing tweaks that shave minutes off your automation workflow. No deep Linux knowledge required — just a willingness to dig into a few settings pages.

---

Understanding Why Medusa Slows Down

Before jumping into fixes, it helps to understand the usual culprits:

• Database bloat: Medusa stores search history, episode metadata, and cache data in an SQLite database. Over time, this database grows and queries slow down.
• Aggressive scheduler intervals: If backlog searches and daily show updates are running too frequently, they compete for CPU and memory simultaneously.
• Unoptimized post-processing: Medusa scanning large directories repeatedly or copying files instead of moving them wastes I/O and slows everything down.
• Too many concurrent providers: Querying dozens of indexers at once hammers your CPU during search runs.

Fixing these is mostly about telling Medusa to work smarter, not harder.

---

Tune Your Scheduler Intervals

The scheduler is the heartbeat of Medusa — it controls when backlog searches, RSS feeds, and show updates run. By default, some of these intervals are more aggressive than they need to be.

Go to Settings > Search Settings > Providers and adjust these:

| Scheduler | Default | Recommended | Notes | |---|---|---|---| | Backlog Search | Every 7 days | Every 3–7 days | No need to run daily for large libraries | | Daily Search | 40 minutes | 60–90 minutes | RSS feeds don't update that fast | | Proper Finder | 90 minutes | 3–4 hours | Propers are rare; no rush | | Failed Snatch Retry | 60 minutes | 2–4 hours | Reduces hammering on failed items |

Spacing these out means Medusa is rarely doing more than one heavy task at a time, which keeps memory usage predictable and CPU spikes short.

---

Optimize the Database Regularly

Medusa's SQLite database (sickbeard.db) is the single biggest performance bottleneck on older installations. Running maintenance on it is straightforward but easy to forget.

Medusa has a built-in tool for this. Head to Settings > Advanced Settings and look for the Rebuild Database option. Running this periodically removes orphaned records and compacts the file.

For a more thorough cleanup, you can also optimize directly via the Medusa web interface at:

http://your-medusa-url/home/databaseInformation

If you're comfortable with the command line inside your SonicBit container terminal, you can also run:

sqlite3 /path/to/your/medusa/data/sickbeard.db "VACUUM;"
sqlite3 /path/to/your/medusa/data/sickbeard.db "ANALYZE;"

VACUUM reclaims disk space and rebuilds the database file. ANALYZE updates the query planner statistics so SQLite picks faster query plans. Run these once a month and you'll notice a real difference on large libraries.

---

Configure Post-Processing for Speed

Post-processing is where Medusa moves or copies downloaded files into your library folders. Done wrong, it's a major bottleneck — especially if you're working with large video files.

Use Move Instead of Copy

Go to Settings > Post-Processing > General and make sure the processing method is set to Move rather than Copy. Copying a 20GB Blu-ray rip takes time and I/O. Moving it (on the same filesystem) is nearly instant.

Set a Dedicated Post-Processing Folder

Point Medusa at a specific completed downloads folder rather than scanning your entire qBittorrent download directory. This keeps scans fast and prevents Medusa from touching in-progress downloads.

Settings > Post-Processing > Post Processing Dir
→ /path/to/qbittorrent/completed/

Disable Auto Post-Processing If You Use Torrent Client Scripts

If qBittorrent is configured to call Medusa's post-processing script on completion (which is the cleanest approach), you don't need Medusa's auto post-processing scanner running on a timer. Turn it off:

Settings > Post-Processing > Auto Post-Processing
→ Disable

This eliminates redundant directory scans entirely.

To trigger post-processing from qBittorrent on completion, add this to qBittorrent's Run external program on torrent completion setting:

curl "http://localhost:8081/home/postprocess/processEpisode?proc_dir=%D&nzbName=%N&process_method=move&force=0&is_priority=0&delete_on=0&failed=0&proc_type=manual" -u username:password

Adjust the port and credentials to match your Medusa setup on SonicBit.

---

Manage Your Provider List

More indexers doesn't always mean better results — it often means slower searches. Medusa queries each provider sequentially (or in small batches), so a list of 20 providers with half of them timing out will make every search feel painful.

Recommendations:

• Keep your active provider list to your 5–8 most reliable indexers
• Disable or remove providers that consistently return errors or timeouts
• Set per-provider timeouts lower (15–20 seconds) so dead providers don't hold up the queue

Go to Settings > Search Settings > Providers and click each provider to adjust its timeout and priority. Providers marked as high-priority get searched first during backlog runs.

---

Control Memory Usage

Medusa is a Python application and doesn't have native memory limits, but you can influence how hard it works.

Limit Concurrent Backlog Searches

Under Settings > Search Settings > Episode Search, reduce the number of simultaneous searches:

Max Simultaneous Searches: 2–3

The default is often set higher, which means Medusa can spin up multiple search threads at once and spike memory during backlog runs.

Cache Management

Medusa caches images and metadata locally. Over time this cache can grow significantly. Check your cache folder size periodically:

du -sh /path/to/medusa/cache/

You can safely clear the images subdirectory — Medusa will re-download missing artwork on next run. Leave the db subdirectory alone.

---

Use Show-Level Backlog Controls

One of the most underused Medusa features is the ability to control backlog behavior per show. If you have older shows that are fully downloaded, tell Medusa to stop searching for them.

Go to each completed show's page and set:

• Status: Ended
• Backlog search: Disable or set to "Ignore"

This prevents Medusa from wasting search cycles on shows that have nothing new to find. For a large library, this alone can cut your backlog search time significantly.

---

Monitor Performance with Medusa's Built-In Logs

When something feels slow, the logs are your best diagnostic tool. Medusa logs timing information for search runs and post-processing tasks.

Navigate to Logs & Errors > Logs and filter by INFO or DEBUG to see how long each task takes. Look for patterns like:

• Providers consistently timing out (remove them)
• Post-processing taking more than 60 seconds (check your folder structure)
• Backlog searches running back-to-back without gaps (adjust scheduler intervals)

Setting the log level to DEBUG temporarily gives you the most detail, but switch back to INFO afterward since DEBUG logging itself has a small performance cost.

---

Putting It All Together

Here's a quick checklist to run through on your SonicBit Medusa instance:

• [ ] Set post-processing method to Move
• [ ] Disable auto post-processing if using torrent client scripts
• [ ] Reduce active providers to 5–8 reliable ones
• [ ] Space out scheduler intervals (daily search to 90 min, backlog to weekly)
• [ ] Run SQLite VACUUM and ANALYZE monthly
• [ ] Limit concurrent backlog searches to 2–3
• [ ] Disable backlog on completed/ended shows
• [ ] Clear the image cache if it's grown large

Most of these changes take less than five minutes each. After applying them, you should notice Medusa feeling more responsive during searches, faster post-processing, and less CPU contention when multiple tasks overlap.

SonicBit handles all the underlying Docker and Traefik complexity automatically, so you can focus entirely on tuning Medusa's settings rather than wrestling with infrastructure. Your Medusa instance gets its own isolated container with dedicated resources — meaning the optimizations you make here have a direct, visible impact.

---

Sign up free at SonicBit.net and get 4GB storage. Download our app on Android and iOS to access your seedbox on the go.