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

Consider using ArraySeq or IndexedSeq instead of List #8

Open
plokhotnyuk opened this issue Sep 19, 2022 · 0 comments
Open

Consider using ArraySeq or IndexedSeq instead of List #8

plokhotnyuk opened this issue Sep 19, 2022 · 0 comments

Comments

@plokhotnyuk
Copy link
Contributor

plokhotnyuk commented Sep 19, 2022 •
edited
Loading

It will improve throughput of parsing and serialization, greatly reduce access time and memory footprint of parsed data, and finally it will reduce GC pressure for better scalability.

Also, potentially, it can simplify parallelization of handling with nested arrays of coordinates.
@plokhotnyuk plokhotnyuk changed the title Consider using ArraySeq instead of List Consider using ArraySeq or IndexedSeq instead of List Sep 30, 2022
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

No branches or pull requests
1 participant
@plokhotnyuk