Repository navigation
Performance
eldor edited this page Nov 12, 2025
·
2 revisions
Optimization guide for ChestLockLite on high-traffic servers.
Run these SQLite commands monthly:
VACUUM;
REINDEX;
ANALYZE;Or use SQLite browser tools to optimize.
- Monitor database file size
- Remove orphaned locks periodically
- Clean up old trusted player entries
- Archive old locks if needed
locks:
max-chests-per-player: 50 # Lower for performance
max-trusted-players-per-chest: 10 # Lower for performancelocks:
allow-passwords: false # If not used
allow-trusted-players: false # If not useddatabase:
backup-interval: 48 # Less frequent backups- Each lock operation is a database write
- Password verification is CPU-intensive (hashing)
- GUI operations are lightweight
- Trusted player checks are fast (indexed queries)
- Limit Max Chests: Prevent players from creating thousands of chests
- Regular Cleanup: Remove abandoned locks periodically
- Monitor Database: Check database size regularly
- Optimize Periodically: Run VACUUM monthly
- Default settings work well
- No optimization needed typically
- Consider limiting max chests per player
- Run database optimization monthly
- Monitor database size
- Lower max chests per player (20-30)
- Limit trusted players per chest (5-10)
- Regular database optimization (weekly)
- Monitor database size closely
- Consider periodic cleanup of old locks
- Database file size
- Number of locks in database
- Average locks per player
- Database query performance
- SQLite browser for database inspection
- Server performance monitoring plugins
- Database query analyzers
- Database optimized (VACUUM)
- Indexes verified
- Max chest limits set appropriately
- Unused features disabled
- Regular maintenance scheduled
- Database size monitored
- Backup strategy in place