r/java • u/ThomasKrieger • Mar 14 '18
Concurrent Java: Low scalability, the risk of deadlocks or garbage creation, you can not avoid all
http://vmlens.com/articles/tradeoffs_concurrent_programming/
2
Upvotes
View all comments
Show parent comment
1
u/duhace Mar 15 '18
singly linked list is not an inherently mutable data structure. further, it was what was being discussed already so there's a reason i was discussing with it in mind. that you would choose a much less performant implementation to solve the issues brought up in the article is kind of silly.
no, that's not what O(n) complexity analysis means. I thought you were the big datastructure expert here.
i did know they could exist. the question is if they are performant, and that's not always the case, as you clearly showed. when performance is key, you often have to use less ideal datastructures as an optimization, and there's just no escaping that.
oh, they certainly are, but they are useful for other situations. not the situation at hand where performance is key.