JPicus@ESE

514 views
467 views

Published on

Presentation of JPicus for Eclipse Summit Europe 2009.

Published in: Technology, News & Politics
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
514
On SlideShare
0
From Embeds
0
Number of Embeds
88
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • TODO picture: Dodge RAM vs. hard drive (a man with a wheel barrow)
  • DEMO
  • “crowded” finally blocks
  • JPicus@ESE

    1. 1. 1JPicus I/O Analysis Framework 1.1 How about I/O ? Kiril Mitov & Pavel Genevski SAP Labs Bulgaria Technology Development
    2. 2. 2JPicus I/O Analysis Framework 1.1 Agenda  Why I/O analysis is important?  JPicus - closing the gap  Why Eclipse?  Summary  Q&A
    3. 3. 3JPicus I/O Analysis Framework 1.1 Why I/O analysis is important?  Moving data in and out of RAM  Throughput and latency  I/O is really slow  Today’s IT trends and I/O analysis  Cloud computing / SaaS  Distributed services  Multi-core & Parallelism Hard drive
    4. 4. 4JPicus I/O Analysis Framework 1.1 JPicus I/O Analysis Framework  JavaTM I/O analysis framework  Non-intrusive  Cross platform  Free JVM Application JPicus Agent -javaagent:jpicus.jar JPicus UI Test/KPI Snapshots
    5. 5. 5JPicus I/O Analysis Framework 1.1 I/O Problem areas  Correctness  File handle leaks  Exhausted file handles  Failed delete operations – can’t delete a file  Undesired delete operations – who deleted a file  Performance  Excessive I/O / bottlenecks  Suboptimal I/O / insufficient buffering
    6. 6. 6JPicus I/O Analysis Framework 1.1 Tips and tricks  Always close your streams  DocumentBuilder.parse(“jar:file:…”)  Equinox: osgi.bundlefile.limit=200  Watch for excessive logging  Watch for “Introvert” module contracts  No nested archives
    7. 7. 7JPicus I/O Analysis Framework 1.1 Why Eclipse?  A mature platform, widely adopted in SAP  Modularization  Many useful features and extension points  Perspectives  Source code navigation  Help system  Widely adopted by the developer community
    8. 8. 8JPicus I/O Analysis Framework 1.1 Possible next steps  TCP & UDP  Comparison of snapshots  Object Query Language (OQL)  SAP JVM / SAP JVM Profiler  You name it!
    9. 9. 9JPicus I/O Analysis Framework 1.1 Summary  I/O Analysis is important  JPicus fills the gap  Give it a try!  JPicus wiki page  http://jpicus.com  Share your experience!  Java Development SDN forum
    10. 10. 10JPicus I/O Analysis Framework 1.1 Thank you Q&A

    ×