![wily introscope monitoring tool interview questions wily introscope monitoring tool interview questions](https://2.bp.blogspot.com/-oiylqiv4ch8/V5GvVDDw8EI/AAAAAAAAAUY/xi8wpNCR58I1R1Zmv0wlUrgoIflTFklRQCLcB/s1600/15.png)
- #WILY INTROSCOPE MONITORING TOOL INTERVIEW QUESTIONS SOFTWARE#
- #WILY INTROSCOPE MONITORING TOOL INTERVIEW QUESTIONS CODE#
![wily introscope monitoring tool interview questions wily introscope monitoring tool interview questions](https://higherlogicdownload.s3.amazonaws.com/BROADCOM/JiveInlineImages/8c7e0e9a02a2411b89d172d5ac5f93d2_Aplication-FrontEnd.png)
#WILY INTROSCOPE MONITORING TOOL INTERVIEW QUESTIONS SOFTWARE#
![wily introscope monitoring tool interview questions wily introscope monitoring tool interview questions](https://higherlogicdownload.s3.amazonaws.com/BROADCOM/JiveInlineImages/2214863ab58f4d0f97b677d63cbf5386_pastedImage_6.png)
Ages are 5,10,15 Average age is / 3= 10 Generations are 3Ģ2 Generations example 2 QuickTimeᆰ and a decompressor are needed to see this picture.Performance Testing Sample Resume Performance Tester Sample Resume Average age is sum of ages / objects Generations are different ages A high generation number might be a memory leak A high age might or might not be a memory leakĢ1 Generations example 1 QuickTimeᆰ and a decompressor are needed to see this picture. Age is the number of times it has survived garbage collection.
#WILY INTROSCOPE MONITORING TOOL INTERVIEW QUESTIONS CODE#
Attach it to the application In Java6 step 1 is not neededġ0 Jconsole Demo QuickTimeᆰ and a decompressor are needed to see this picture.ġ1 Topics Software Quality with FindBugs Using Jconsole Monitoring with Netbeans 6 Profiling CPU with Netbeans 6 Profiling Memory with Netbeans 6 Conclusionġ2 Netbeans 6 profiler suite Integrated into Netbeans by default Basic information (similar to jconsole) CPU analysis (hotspots) Memory analysis (memory leaks) Used to optimize a correct program Imposes overhead on the applicationġ3 Basic profiling Offers information similar to jconsole Heap size Threads Classes loaded Minimal overhead for the application Used for an overviewġ4 Basic profile Demo QuickTimeᆰ and a decompressor are needed to see this picture.ġ5 Topics Software Quality with FindBugs Using Jconsole Monitoring with Netbeans 6 Profiling CPU with Netbeans 6 Profiling Memory with Netbeans 6 Conclusionġ6 CPU profiling Optimize always the frequent code Use CPU profile to find this code 20% of the code runs 80% of time Optimize this 20% Medium overhead for the application Also see time spent for GC/IO/Gui e.t.c.ġ8 Topics Software Quality with FindBugs Using Jconsole Monitoring with Netbeans 6 Profiling CPU with Netbeans 6 Profiling Memory with Netbeans 6 Conclusionġ9 Memory profiling Java code suffers from memory leaks Minor leaks (objects allocated once) Major leaks (object allocated multiple times) Garbage collector is your friend Difficult to distinguish memory leaks from long-lived objects Maximum overhead for the applicationĢ0 Introducing Generations Each object has an age. heap size) Threads (active/total) Classes Loaded JVM environment propertiesĩ Jconsole usage 1. Unclosed Streams Security Problems Fields that should be static Performance problems Possible null pointers More.Ħ FindBugs Demo QuickTimeᆰ and a decompressor are needed to see this picture.ħ Topics Software Quality with FindBugs Using Jconsole Monitoring with Netbeans 6 Profiling CPU with Netbeans 6 Profiling Memory with Netbeans 6 ConclusionĨ Jconsole Introduced in Java 5 (experimental) Enhanced in Java 6 Shows basic information for JVM Memory (e.g. 3 Topics Software Quality with FindBugs Using Jconsole Monitoring with Netbeans 6 Profiling CPU with Netbeans 6 Profiling Memory with Netbeans 6 ConclusionĤ Software quality tools FindBugs PMD CheckStyle Run from command line Use GUI (even webstart) Integrate into Netbeans/Eclipse Detect problematic situationsĥ Problematic situations Ignoring return values from methods.