Jump to: navigation, search

User:Michael.f.obrien.telus.com

Revision as of 15:47, 20 June 2011 by Michael.f.obrien.eclipselink.org (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

bugzilla id: michael.f.obrien(at)telus.com

committer id: mobrien (F. Michael O'Brien)

Location: Ottawa, Canada - Eastern Standard Time

  • Committer on Eclipse Persistence Services project - EclipseLink

Profession: Overly enthusiastic and optimistic Enterprise Software Developer

Currently working with Telus Health | backed by Emergis on their Oacis since April 2011 after a very good 5 years with Oracle Corporation on their TopLink product and the Eclipse Foundation on their EclipseLink product. Specialized in Application Server Container deployments, JMX and the Metamodel API in the latest JSR-317 JPA 2.0 API RI for the JEE6 specification.

References

Misc

EE Tutorial Pages

EclipseLink related Forums

Software References

Hardcover

Experimental


Activity

Official

Indirectly/Adjacent/Followup/Assist

Interest

Dynamic Persistence

Architecture Aware Computing

SaaS | PaaS | IaaS

Concurrency Issues

UnOfficial

Deferred but Very Important

Pending

Raised

Bugs and Enhancements I am interested in

Experimental

  • 20110209: Distributed JPA application using multiple SE clients connected to a single EE server using various EJB/RMI, JMS, JAX-RS and WebServices technologies. Use this distributed framework to hammer the JTA container managed persistence context and observe how it handles concurrency contention.
  • Concurrency
  • Thread safety
  • Mixed JSF/Spring/AJAX/EJB framework artifacts
  • Hibernate JPA and WebLogic

To Review

Statistics

Specifications

Theory

Links

Log

  • 20101231:3188
  • 20100908: rewrite started at hit 2620
  • Everybody would like to optimize computations in their spare time - but using all available capacity of your servers is not an easy thing to do. Don't let let your multicore processor sit idle or use a small percentage of it's potential - use threads and push your processor to it's limit of parallel computation and use of electrical resources. Pass this very interesting graphic to all your Java, C++, C, Assembly and even Smalltalk friends. Don't worry about locking, deadlock, thread contention, thread scheduling, finished threads waiting on slower threads, data corruption, queuing, synchronization, concurrency issues, data parallel work distribution/merging, heat dissipation, and electicity usage - as everything can be solved.

Corei7 920 zoom time 1 to 512 threads graph.JPG