89         The current jlong tag being used on allocated objects
  90         is an ObjectIndex, or an index into the object table inside
  91         the hprof code. Depending on whether heap=sites or heap=dump 
  92         was asked for, these ObjectIndex's might represent unique
  93         objects, or unique allocation sites for types of objects.
  94         The heap=dump option requires considerable more space
  95         due to the one jobject per ObjectIndex mapping.
  96 
  97     * BCI Performance
  98         The cpu=times seems to have the most negative affect on
  99         performance, this could be improved by not having the 
 100         Tracker class methods call native code directly, but accumulate
 101         the data in a file or memory somehow and letting it buffer down
 102         to the agent. The cpu=samples is probably a better way to
 103         measure cpu usage, varying the interval as needed.
 104         The heap=dump seems to use memory like crazy, but that's 
 105         partially the way it has always been. 
 106 
 107     * Sources in the JDK workspace
 108         The sources and Makefiles live in:
 109                 src/share/classes/com/sun/demo/jvmti/hprof/*
 110                 src/share/demo/jvmti/hprof/*
 111                 src/share/demo/jvmti/java_crw_demo/*
 112                 src/solaris/demo/jvmti/hprof/*
 113                 src/windows/demo/jvmti/hprof/*
 114                 make/java/java_hprof_demo/*
 115                 make/java/java_crw_demo/*
 116    
 117 --------

  89         The current jlong tag being used on allocated objects
  90         is an ObjectIndex, or an index into the object table inside
  91         the hprof code. Depending on whether heap=sites or heap=dump 
  92         was asked for, these ObjectIndex's might represent unique
  93         objects, or unique allocation sites for types of objects.
  94         The heap=dump option requires considerable more space
  95         due to the one jobject per ObjectIndex mapping.
  96 
  97     * BCI Performance
  98         The cpu=times seems to have the most negative affect on
  99         performance, this could be improved by not having the 
 100         Tracker class methods call native code directly, but accumulate
 101         the data in a file or memory somehow and letting it buffer down
 102         to the agent. The cpu=samples is probably a better way to
 103         measure cpu usage, varying the interval as needed.
 104         The heap=dump seems to use memory like crazy, but that's 
 105         partially the way it has always been. 
 106 
 107     * Sources in the JDK workspace
 108         The sources and Makefiles live in:
 109                 src/jdk.hprof.agent/*

 110                 src/share/demo/jvmti/java_crw_demo/*
 111                 make/lib/Lib-jdk.hprof.agent.gmk



 112    
 113 --------