Jump to content

Discussion Question about Threads in L2J


Recommended Posts

When you create a task to be executed in X time, does the thread burden the pool or the OS even in that X time or only at the execution? Who is responsible for the countdown of that X time?

Edited by Hustman
Link to comment
Share on other sites

  • Hustman changed the title to Question about Threads in L2J

If you properly use L2J ThreadPoolManager implementation, you simply pick a thread from an existing pool and once executed it returns to the pool - similar to a db connection factory.

 

L2J implementation is nothing more than dedicated ThreadPoolExecutor / ScheduledThreadPoolExecutor, 4 of each types.

 

You can read more on Google, as introduction

https://www.baeldung.com/thread-pool-java-and-guava

https://www.geeksforgeeks.org/thread-pools-java/

 

And whatever related to ThreadPoolExecutor / ScheduledThreadPoolExecutor classes.

Link to comment
Share on other sites

15 hours ago, Tryskell said:

If you properly use L2J ThreadPoolManager implementation, you simply pick a thread from an existing pool and once executed it returns to the pool - similar to a db connection factory.

 

L2J implementation is nothing more than dedicated ThreadPoolExecutor / ScheduledThreadPoolExecutor, 4 of each types.

 

You can read more on Google, as introduction

https://www.baeldung.com/thread-pool-java-and-guava

https://www.geeksforgeeks.org/thread-pools-java/

 

And whatever related to ThreadPoolExecutor / ScheduledThreadPoolExecutor classes.

Thank you for answering, very instructive article. However, I am unable to locate in the ScheduledThreadPoolExecutor section, who is responsible for the delay countdown. Does the thread also perform this function? Does this mean that it uses CPU resources even before executing?

Edited by Hustman
Link to comment
Share on other sites

The thread is simply an executable class, the ScheduledThreadPoolExecutor handles the management of it. How ? Who cares, it was optimized for you by some high-grade dudes years ago and added directly in Java.

 

Seeing how much tasks are generated by seconds (network, AI, and random tasks), it probably costs almost none CPU/RAM. You only have to assure yourself to avoid to bottleneck the system.

 

Not sure why you need this answer, your best bet is to make tests yourself because litteraly none did that before you (at least, I didn't).

Link to comment
Share on other sites

What you can try to do is to change dynamically each executor's thread size based on your current cpu usage (ThreadPoolExecutor#setCorePoolSize). Although, i don't think that you will need such an optimization.

Link to comment
Share on other sites

4 hours ago, Zake said:

What you can try to do is to change dynamically each executor's thread size based on your current cpu usage (ThreadPoolExecutor#setCorePoolSize). Although, i don't think that you will need such an optimization.

The only thing I want to know is, who is responsible for the countdown of the delay, that's all.

Link to comment
Share on other sites

  • 3 months later...

new thread waits for execute runnable. It means jvm calling OS for new thread when you create scheduled execution (that's for single Timer). ScheduledThreadPoolExecutor works asynchronously 

Edited by amaranthe92
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share



×
×
  • Create New...

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock