The following operators can be used to better focus your queries.
( ) , AND, OR, NOT, W/#
? single char wildcard, not at start
* multi char wildcard, not at start
(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*
This guide provides a more detailed description of the syntax that is supported along with examples.
This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.
Concept Search - What can I type?
For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.
Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.
A method for maintaining and utilizing thread based call stacks using Java entry/exit events to maintain Interpreted versus JITed state
English (United States)
This text was extracted from a PDF file.
This is the abbreviated version, containing approximately
88% of the total text.
Page 1 of 1
User-level Sampling Using Thread Entry and Exit Events
Disclosed is a method for maintaining and utilizing thread based call stack information using entry/exit events that identify the method calls or entries as being to Interpreted or Just-In-Time (JITed) compiled methods.
Using the existing IBM(*) extensions to the Java(**) Virtual Machine (JVM) Application Programming Interfaces (APIs) supported in the Java Virtual Machine Profiling Interface (JVMPI) or the Java Virtual Machine Tools Interface (JVMTI), the entry events distinguish between an entry to a JITed method or a method that is being executed interpretively. This information is helpful in analyzing the time spent executing in individual methods and provides more details regarding the opportunities for improving performance.
By enabling the IBM extensions for entry/exit events, thread based call stacks are maintained for each monitored thread by pushing the entry event information onto a stack in memory and popping the information off the stack when the exit event occurs. Specific conditions may be monitored, such as, the number of instructions between two events or the number of bytes allocated by monitoring object allocation events. When the monitored conditions occur, the maintained calling sequence can be used to walk the information into a thread based call tree where a counter in the leaf node of the tree is incremented to indicate a sample occurred. Reports...