Skip to content
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.

Sign up for GitHub

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

Jump to bottom

make DBLOGUtil.getTimestepIndex() efficient #105

Closed
cberzan opened this issue May 19, 2014 · 1 comment
Closed

make DBLOGUtil.getTimestepIndex() efficient #105

cberzan opened this issue May 19, 2014 · 1 comment
Labels
optimization refactoring

Comments

@cberzan
Copy link
Contributor

cberzan commented May 19, 2014

Possible starter task for @chrisgioia64.

Profiler run shows that DBLOGUtil.getTimestepIndex() indirectly does a lot of memory allocation. It converts the BayesNetVar to a String, and then does a regex match on the String to extract the timestep the variable refers to. Very inefficient. There should be an easier way to get the timestep out of a BayesNetVar.
@cberzan
Copy link
Contributor Author

cberzan commented Jul 2, 2014

Fixed with the introduction of ArgSpec.maxTimestep()

@cberzan cberzan closed this as completed Jul 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
optimization refactoring
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cberzan