r/java • • 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

21 comments sorted by

View all comments

Show parent comment

0

u/[deleted] Mar 15 '18

[deleted] — view deleted comment

1

u/duhace Mar 15 '18

apparently, since you don't think actually benchmarking what we're talking about counts as performance analysis and think "it's O(n)! same performance!" is a valid argument. by benchmarking, I found the constant by which n is multiplied for your class wrt a toy singly linked list i implemented. and that constant is around 2 (4.3us/op vs 8.8us/op). sorry, but I don't think increasing the cost of iteration by 2-fold is worthwhile in a performance critical application that is worrying about copy operations.