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

Inefficient Usage of JCF #1080

Closed
FastAtlas opened this issue Sep 6, 2021 · 1 comment · Fixed by #1079
Closed

Inefficient Usage of JCF #1080

FastAtlas opened this issue Sep 6, 2021 · 1 comment · Fixed by #1079
Milestone

Comments

@FastAtlas
Copy link
Contributor

Hi,

We find that there are several ArrayList objects which are not manipulated by random access. Due to the memory reallocation triggered in the successive insertions, the time complexity of add method of ArrayList is amortized O(1). We notice that these objects are only used for traversal, the retrieval, and removal of the first or the last element.

This functionality can be implemented by LinkedList. Moreover, the insertion of LinkedList is strictly O(1) time complexity because no memory reallocation occurs.

Meanwhile, we also found several LinkedHashSet and LinkedHashMap objects which are not necessary to maintain the order of insertions. To achieve the same functionality, HashHap and HashSet are enough. The replacement can also reduce the time cost in the modification of the map objects.

We discovered the above inefficient usage of containers by our tool Ditto. The patch is submitted in #1079. Could you please check and accept it? We have tested the patch on our PC. The patched program works well.

Bests

Ditto

@OrezzerO
Copy link
Contributor

OrezzerO commented Sep 7, 2021

Thank you for your PR, we will check the changes later.Performance is important for us, your work can help us a lot

@EvenLjj EvenLjj linked a pull request Sep 18, 2021 that will close this issue
@EvenLjj EvenLjj added this to the 5.8.0 milestone Sep 18, 2021
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

Successfully merging a pull request may close this issue.

3 participants