Posted by Coder.
Posted by Coder.
Jon Masamitsu’s Weblog : Weblog
“…basic concepts, some specifics about our GC, suggestions on tuning, and some of the latest improvements such as the parallel old collector…”
http://java.sun.com/j2se/reference/whitepapers/memorymanagement_whitepaper.pdf
Posted by Coder.
O’Reilly Open Source Convention – July, 24-28, 2006 – Portland, OR
Open Source Performance Monitoring Tools and Tricks for Java
Speaker: Matt Secoske (07/28/2006)
Download presentation files
Eight Steps to Fix Your Database Performance Problem
Speaker: Christopher Browne (07/27/2006)
Download presentation files
Posted by Coder.
ASPs: The Integration Challenge
The main problem with performance when using the APIs provided by ASPs is the per-call overhead. The overhead comes from latency over the Internet, transmission time, marshalling (xml/SOAP) requests on the client side and responses on the ASP side, un-marshalling (xml/SOAP) requests on the ASP side and responses on the client side, and authentication/authorization checking and other overhead at the ASP.
In accessing Salesforce.com and CRM OnDemand (both of these ASPs are located in North America, as are …
Posted by Coder.
More tiered compilation
… a repository of information collected from one run and used on another run is on the list for things we want to do in Dolphin. It’s actually on the runtime groups list but we will certainly take advantage of it. There has also been talk of using annotations to give the jit a hint. This actually isn’t too popular since it is too much like “register” declarations in C. It’s only a hint and is too often …
Posted by Coder.
Java Portability
…this program below does nothing visible on Solaris, but prints “hello” with Sun Java SE on Linux and Windows:
public class Foo {
public static void main(String[] args) {
Thread.currentThread().interrupt();
System.out.println(”hello”);
}
}
First impressions of this program’s behavior on Solaris roughly translate to “The hell you say!” followed by “Java is broken on Solaris!” There are a number of “symptoms” of interruptible I/O that catch users off guard and in a few cases one is led to wonder if it might be best to do …
Posted by Coder.
Scott Dorman — Windows Vista: Kernel Changes – Shadows of Reliability, Performance and Scalability
Vista makes fewer and larger disk reads for page faults and system cache read-ahead and has removed the 64KB limit. Fewer, faster, and larger disk writes for the system page file and mapped file I/O reduce the page file fragmentation and allow a larger cluster size.
The CPU usage has also been improved by providing improvements in the concurrency management within the kernel.
Posted by Coder.
Musings on software » Why choose cmp
…consider the strengths in performance and reduction in development that can be added by leveraging a high-quality CMP container as opposed to developing data access logic using a BMP architecture. I guarantee you’ll be happy with the results.
Excellent post! I couldn’t agree more, the debate mirrors the one around the merits and usefulness of automatic garbage collection. Sure you can manage memory yourself, but how much are you willing to pay for that vs. …
Posted by Coder.
Stanford talk
Pat Gelsinger discusses motivations that drove the development of the Intel® Core™ Microarchitecture, some of its most important features and the challenges that face microprocessor designers in the future.
[See video]
Posted by Coder.
IBM developerWorks : Blogs : Software architecture, software engineering, and Renaissance Jazz
I am inside the ICU at Mayo clinic, just a few hours after my open heart surgery. Steve, my ICU registered nurse, is my eyes and fingers typing this blog. As you can tell by the very fact that I am blogging I am not dead yet.
Wishing you a speedy recovery.
Posted by Coder.
Stefan Kaes, author of the forthcoming book, “Performance Rails”, scheduled to publish in early 2007, has this to say about Rails performance …
InfoQ – Tracking change and innovation in the enterprise software development community
… [areas where] applications [fall] short of achieving good performance.
choosing a slow session container
doing things on a per request basis, which could have been done once at startup
repeating identical computations during request processing
reading too often and too much from the database (especially in conjunction with associations)
relying too …