📊 Performance Considerations

Optimization Features

1. Proximity Calculation

   • O(n) complexity per message

   • Entity coordinate caching

   • Efficient distance calculation

2. Config Loading

   • JSON cached in memory

   • Lazy loading of Discord data

   • Async API calls with timeouts

3. Player Data Caching

   • Cached on join

   • Cleaned on disconnect

   • Periodic refresh for roles only (30 min)

4. React UI

   • Optimized re-renders

   • Message grouping reduces DOM nodes

   • Efficient state management

Resource Usage

• Memory: ~50-100MB (depending on player count)

• CPU: Minimal impact (<1% per message)

• Network: Efficient event broadcasting

• Disk: Config file only (~10-50KB)

Performance Benchmarks

Metric	Value
Proximity calculation (100 players)	<5ms
Config load	<10ms
Config save	<50ms
Discord API fetch	<200ms (with cache)
Message broadcast	<1ms

Best Practices

1. Limit Chat Modes: Don't create too many modes (recommended: <20)

2. Reasonable Cooldowns: Use cooldowns to prevent spam

3. Proximity Ranges: Keep distances reasonable (<100m)

4. Config Validation: Always validate before major changes

5. Backup Config: Backup before experimenting