Use thread pools instead of new threads every time a command runs #6
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Starting threads is very expensive, although acceptable for now to help with JDA's thread-blocking methods. However, using pools with workers would be way better.
Useful Link
Also look into:
Executors.newScheduledThreadPool(), but this might be more useful for the scheduled tasks (as the name suggests) like expired messages, trivia, heartbeat...