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

possible optimization for allocating memory to segments and pixel segments differently #229

Open
YonsiG opened this issue Jan 3, 2023 · 0 comments
Open

possible optimization for allocating memory to segments and pixel segments differently #229

YonsiG opened this issue Jan 3, 2023 · 0 comments

Comments

@YonsiG
Copy link
Contributor

YonsiG commented Jan 3, 2023

As discussed in PR. If we want to study the memory footprint in more detail, it's good to separate the pixel segment and out-tracker segments so that we can allocate different memories for the two objects, but now we are using the same variable.
@YonsiG YonsiG linked a pull request Jan 3, 2023 that will close this issue
Clean up N_MAX memory #222
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clean up N_MAX memory YonsiG/TrackLooper
1 participant
@YonsiG