5:54 p.m.
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking behavior
in the interceptors make it possible to end up w/ 2 concurrent nodes for the same Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:27 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]
Manik Surtani updated JBCACHE-811:
----------------------------------
Fix Version/s: 2.1.0.GA
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.1.0.GA
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:44 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]
Manik Surtani updated JBCACHE-811:
----------------------------------
Fix Version/s: 2.2.0.GA
(was: 2.1.0.GA)
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.2.0.GA
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 p.m.
New subject: [JBoss JIRA] Assigned: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]
Manik Surtani reassigned JBCACHE-811:
-------------------------------------
Assignee: Mircea Markus (was: Manik Surtani)
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Mircea Markus
Fix For: 2.2.0.GA
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:54 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]
Manik Surtani updated JBCACHE-811:
----------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.2.0.GA)
Assignee: Manik Surtani (was: Mircea Markus)
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.1.0.GA
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:08 p.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]
Manik Surtani resolved JBCACHE-811.
-----------------------------------
Fix Version/s: 2.1.0.CR3
Resolution: Done
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.1.0.CR3, 2.1.0.GA
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:14 a.m.
New subject: [JBoss JIRA] Reopened: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]
Manik Surtani reopened JBCACHE-811:
-----------------------------------
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 2.1.0.CR3
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:16 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]
Manik Surtani updated JBCACHE-811:
----------------------------------
Fix Version/s: 2.2.0.GA
(was: 2.1.0.GA)
(was: 2.1.0.CR3)
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.2.0.GA
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:16 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[ http://jira.jboss.com/jira/browse/JBCACHE-811?page=comments#action_12398381 ]
Manik Surtani commented on JBCACHE-811:
---------------------------------------
Backed this out from 2.1.x as the initial implementation was a major perf hog. It was
actually quicker to repeat the peek as and when necessary - mainly to do with the
map.put() and get() operations caching the relevant nodes in the InvocationContext, keyed
on Fqn (which is expensive when it comes to equals() and hashCode())
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.2.0.GA
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:58 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]
Manik Surtani updated JBCACHE-811:
----------------------------------
Fix Version/s: 3.0.0
(was: 2.2.0.GA)
Moving this to 3.0.0, as this is where it will really be needed with MVCC.
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 3.0.0
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:45 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]
Manik Surtani updated JBCACHE-811:
----------------------------------
Fix Version/s: 3.0.0.ALPHA1
Note that this optimisation is only for MVCC. Other locking schemes won't use this.
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: http://jira.jboss.com/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 3.0.0.GA, 3.0.0.ALPHA1
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:14 p.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node
[
https://jira.jboss.org/jira/browse/JBCACHE-811?page=com.atlassian.jira.pl...
]
Manik Surtani resolved JBCACHE-811.
-----------------------------------
Resolution: Done
Use InvocationContext to avoid multiple searches for a node
-----------------------------------------------------------
Key: JBCACHE-811
URL: https://jira.jboss.org/jira/browse/JBCACHE-811
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assignee: Manik Surtani
Fix For: 3.0.0.ALPHA1, 3.0.0.GA
When an interceptor finds a node, why not throw it in the InvocationContext or something
similar and pass it through the stack that way? Subsequent calls to find the node can
check the context first before walking the cache tree. Saves redundant walking of the
tree.
We'd need to think very carefully about this, as it exposes 2 paths to access a node
-- from a thread's context and from the tree. Need to ensure concurrent threads
always access the same node object for a given Fqn.
(Side thought -- perhaps disable this for weak isolation levels where the locking
behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same
Fqn).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5909
days inactive
6539
days old
11 comments
2 participants
participants (2)
-
Brian Stansberry (JIRA) -
Manik Surtani (JIRA)