Women in Technology

Hear us Roar



Article:
  Scaling Enterprise Java on 64-bit Multi-Core X86-Based Servers
Subject:   No really reasonable suggestion
Date:   2006-11-03 20:49:34
From:   michael_yuan
Response to: No really reasonable suggestion

Kutzi,


Hmm, first and foremost, I am suggesting developers to take advantage of Java 5.0 APIs in their own applications.


Now, if the application server itself has concurrency issues, I understand that the average application developer would not know how to fix it. But you can at least find the contention point in the source code (in the case of an open source app server) and raise a issue (bug report or feature request) to the open source developers in that community ...

Full Threads Newest First

Showing messages 1 through 1 of 1.

  • No really reasonable suggestion
    2006-11-06 05:54:16  kutzi [View]

    > first and foremost, I am suggesting developers to take advantage of Java 5.0 APIs in their own applications.

    Yes, that is certainly a good thing to do, but not "whenever possible" as you said, but only if the gains outweigh the risks. E.g. util.concuurent.Locks are faster than synchronized blocks, but they bear the additional risk of forgetting to release it. And, as Goetz says in Java Concurrency in practice, perfomance is a moving target. While Locks used to be much faster than synchronized, in Java 6 the gap has nearly closed.