-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve CPU utilization for long running fitness functions #197
Comments
Hi, where can I get a preview? Do you will create a new branch? |
jenetics
added a commit
that referenced
this issue
Apr 23, 2017
jenetics
added a commit
that referenced
this issue
Apr 23, 2017
The value can be changed with the 'io.jenetics.concurrency.splitThreshold' system property.
jenetics
added a commit
that referenced
this issue
Apr 23, 2017
The value can be changed with the 'io.jenetics.concurrency.maxBatchSize' system property.
jenetics
added a commit
that referenced
this issue
Apr 23, 2017
jenetics
added a commit
that referenced
this issue
Apr 23, 2017
jenetics
added a commit
that referenced
this issue
Apr 23, 2017
jenetics
added a commit
that referenced
this issue
Apr 23, 2017
jenetics
added a commit
that referenced
this issue
Apr 23, 2017
jenetics
added a commit
that referenced
this issue
Apr 24, 2017
jenetics
added a commit
that referenced
this issue
Apr 24, 2017
jenetics
added a commit
that referenced
this issue
Apr 24, 2017
Merged into r3.8.0 branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jenetics is calculating the fitness values for each generation concurrently. The main assumption is, that the calculation of the fitness function is relatively cheap and the calculation costs are constant for all genotypes. With this assumption in mind, the population is split into sub-populations, which group the fitness function into bigger evaluation units. This should reduce the evaluation overhead. If we have to deal with long-running fitness functions, or with fitness function with unpredictable computation costs, the existing computation strategy no longer works as expected. We get idle CPU cores.
This ticket is about to improve the CPU utilization for long-running fitness functions and for fitness functions with non-constant evaluation costs.
See
#196
Hint
Consider usage of getSurplusQueuedTaskCount() method.
The text was updated successfully, but these errors were encountered: