DESCRIPTION

ctf: Lttng specific performance improvement

CTF based Lttng traces have 30-40% of their requests directed to the
same fields, this makes seeking these fields faster.

Change-Id: I3cf32b10d22de04a1bd94ecadde37afa8e50b0a1
Signed-off-by: Ivy Mitchell xxx@xxx.xxx


COMMENTS

author: Ivy Mitchell
date: 2014-05-02 04:07:29.000000000

Uploaded patch set 1.

-------------------------------------
author: Brenden Conley
date: 2014-05-02 06:24:29.000000000

Patch Set 1:

Build Started https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/6808/

-------------------------------------
author: Brenden Conley
date: 2014-05-02 07:06:56.000000000

Patch Set 1: Verified+1

Build Successful 

https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/6808/ : SUCCESS

-------------------------------------
author: Ivy Mitchell
date: 2014-05-02 12:16:37.000000000

Topic set to Ctf performance

-------------------------------------
author: Ivy Mitchell
date: 2014-05-02 12:19:53.000000000

Topic changed from Ctf performance to CTF performance

-------------------------------------
author: Braxton Mccarthy
date: 2014-05-02 17:07:36.000000000

Patch Set 1: Code-Review-1

(1 comment)

Can make sense to have a specific class for a specific type of scope, especially if it makes the common case go faster.

However, what's the difference between a scope and a vscope? The Javadoc in both classes could be elaborated a bit.

Line:48, lttng/org.eclipse.linuxtools.ctf.core/src/org/eclipse/linuxtools/ctf/core/event/scope/PacketHeaderVScope.java -> wut

-------------------------------------
