CDV ❯ Improve performance of collections.sort - seems that each positional change is resulting in a transaction (can that be batched ?)
-
Bug
-
Status: Closed
-
2 Major
-
Resolution: Fixed
-
-
-
teck
-
Reporter: siyer
-
October 05, 2007
-
0
-
Watchers: 1
-
July 27, 2012
-
April 22, 2008
Description
Comments
Tim Eck 2007-10-05
Tim Eck 2007-10-05
that code path could be optimized for its calls to ArrayManager checks, but I don’t see any evidence of needless dso txns
Fiona OShea 2007-10-09
Can you provide an example as requested by tim?
Fiona OShea 2008-01-11
Any status update?
Fiona OShea 2008-01-18
Iyer has some code for you
Fiona OShea 2008-01-21
This appears to be addressed in Dist Use Case Project. See Use Case#6 in design doc. http://intranet.terracotta.lan/xwiki/bin/view/Main/Design+Docs/DistCacheDesign.odt
Fiona OShea 2008-04-22
fixed by completion of dist cache use cases.
any chance you can provide an example? I’m mostly curious if a locked collection is being sorted in this case (ie. sometihng like Vector or Collections.synchronizedXXX())
The code of sort() shouldn’t do any transactions in and of itself, but it can call set() on the list being sorted (which if autolocked) will define a txn