Taken from the Apache TreeList doc:
The following relative performance statistics are indicative of this class:
get add insert iterate remove TreeList 3 5 1 2 1 ArrayList 1 1 40 1 40 LinkedList 5800 1 350 2 325
It goes on to say:
LinkedListis rarely a good choice of implementation.TreeListis almost always a good replacement for it, although it does use sligtly more memory.
My questions are:
What is with the
ArrayListadd,insert, andremovetimes crushingLinkedList? Should we expect, for one, that real-world insertion and removal cases greatly favorArrayList?Does this
TreeListsimply put the nail in the coffin of the venerableLinkedList?
I am tempted to conclude they have amortized or ignored ArrayList's growing pains, and have not taken into consideration the insertion and removal times for an item in a LinkedList that has already been located.