Skip to main content

⚡ Server Optimizations

Hello there! Welcome to the guide about Server Optimization for Open Ticket. This guide will help you scale Open Ticket efficiently for large Discord servers.

Running Open Ticket on a small server is easy, but when your server grows to thousands of members, things like database efficiency and hosting power become more important.

Here, we’ll cover the best ways to keep your bot running smoothly!

Optimizations

For huge and busy Discord servers

💾 System Requirements​

If you're running Open Ticket in a large server, shared hosting or low-end VPS setups may not be enough. Here's what you should consider:

  • CPU & RAM: Open Ticket is lightweight, but make sure you have at least 1-2 CPU cores and 1GB+ RAM.
  • Disk Type: A SSD or NVMe drive is recommended, especially if you’re using a local (json or sqlite) database.
  • Uptime & Stability: Consider using a dedicated VPS with good uptime.

Minimum (Small Servers)​

  • OS: Windows, MacOS, Linux
  • Node.js: v18+ (Download)
  • Memory (Peaks): 600MB
  • Memory (Idle): 100MB
  • Storage/SSD: 200MB
  • Good internet connection
  • VPS with good uptime

Is Optimized For​

  • Members: 1 - 500
  • Ticket Rates: ~10/hour
  • Message Activity: ~200/hour
  • OS: Linux
  • Node.js: v22+ (Download)
  • Memory (Peaks): 2GB
  • Memory (Idle): 300MB
  • Storage/SSD: 1GB
  • Good internet connection
  • VPS with good uptime

Is Optimized For​

  • Members: 500 - 50k
  • Ticket Rates: ~200/hour
  • Message Activity: ~5000/hour

Overkill (Huge Servers)​

  • OS: Linux
  • Node.js: v22+ (Download)
  • Memory (Peaks): 5GB
  • Memory (Idle): 1GB
  • Storage/SSD: 5GB
  • Good internet connection
  • VPS with good uptime

Is Optimized For​

  • Members: 50k - 100k
  • Ticket Rates: ~500/hour
  • Message Activity: ~10k/hour

🗄️ SQLite Database​

By default, Open Ticket stores data in JSON files. While this works for small servers, it can slow down with thousands of tickets. Switching to an SQLite database improves speed and reliability.

For most servers, SQLite is a great alternative to JSON. It’s lightweight and doesn’t need extra setup.

  • ✅ Faster ticket loading and saving
  • ✅ Faster command responses
  • ✅ Reduces file corruption risks
  • ✅ No external database server needed

🛠️ Optimizing Plugins & Features​

Not all features are needed for every server. Disabling unnecessary options reduces CPU & memory usage.

🔧 Reduce Heavy Features​

  • Disable Unused Commands: If you don’t use certain commands, disable them in the settings.
  • Limit Active Options: Too many different options will slow down the bot.
  • Limit Active Panels: If you have many ticket panels, only keep the essential ones.
  • Disable Logs: If the ticket logs slow down the bot a lot, consider turning them off.

🎯 Set Limits​

  • Enable Global Limits: Only one ticket per user.
  • Enable Ticket Limits: Only one ticket per user per ticket/option type.
  • Enable Ticket Cooldowns: Users can create a ticket and have to wait an hour to create the next one.

🏆 Summary​

Now you know:
✅ How to optimize Open Ticket.
✅ How to properly host Open Ticket on a VPS.
✅ Which plugins to use for large servers.

⭐ awesome ⭐

Don't forget to give Open Ticket a star on GitHub to help us grow!

Next Steps​

Learn More​