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.

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

about memory #15

Open
HeXu1 opened this issue Oct 29, 2020 · 2 comments
Open

about memory #15

HeXu1 opened this issue Oct 29, 2020 · 2 comments

Comments

@HeXu1
Copy link

HeXu1 commented Oct 29, 2020

hi,thanks for your great work.

what's the memory consumed mainly? it seems my 16G memory almost be used,but the robot doesn't move so far.

hope for your reply,thanks

@wh200720041
Copy link
Owner

Hi @HeXu1

The memory is mainly consumed by input laser cloud and mapping. The loop closure detection checks for all input frames instead of key frames. Hence all historical point clouds are stored into memory.

A new version is updated and I did some modification to reduce the point cloud size when stored into database.

If you are trying to use it for long term localization, maybe you should consider to store key frames only for loop closure detection

@HeXu1
Copy link
Author

HeXu1 commented Nov 9, 2020

Hi,I will test it. thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants