cyclicbarrier creates lots of garbage?
--------------------------------------
Key: CDV-922
URL: https://jira.terracotta.org/jira//browse/CDV-922
Project: Community Development
Issue Type: Bug
Reporter: Taylor Gautier
Assignee: Issue Review Board
Probably not a big deal, but it seems every await() call in CyclicBarrier
creates a new object.
See the attached screenshot for a test that runs a cyclicbarrier with 5
processes/threads. The overall rate of barrier acquisition is between 20-30,
which corresponds very well with the object creation rate, e.g. 5*20 is 100,
which is the object flush and fault rate, indicating to me that new objects are
used to indicate an arrival of a thread (I haven't seen the code - maybe they
are being put into a map?)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
