Posted by coder.
Results > Posts Filed Under > Java
Feb
10
Posted by coder.
1
Sun Dialogue Programs
(Q): If you have to pick top 10 things that you must monitor on any server to look for performance and/or scalability issues…what would they be?
Richard McDougall (A): Off the top of my head, in no particular order:
CPU: Check idle time and run queue length.
If there’s a CPU bottleneck, check if it’s an application or kernel CPU utilization issue with mpstat: high percentages of users indicate it’s an application issue. High sys may point to high network load …
Jan
6
Posted by Coder.
This research note shows the “Magic Quadrant”. Wily (now CA), IBM, Veritas, Mercury and Quest are at the top in terms of “ability to execute” and “vision”…
Jan
6
Posted by coder.
Servlet Performance Report: Comparing Tomcat Performance Across Platforms
Prior to reaching capacity, our Linux server showed it’s ability to scale subtly better, notably with a higher completed response rate. This trend arises again after the servers have been able to recover from their performance slump.
When our servlet found itself hitting memory limits of the app server, the platforms had an opportunity to reveal different error handling techniques. Linux maintained it’s lead over it’s Windows counterpart, except when it was …
Jan
6
Posted by coder.
Performance Scalability of Data-Mining Workloads in Bioinformatics, from Intel – White Papers, Webcasts, and Case Studies – ITPapers
Data mining is the extraction of hidden predictive information from large data bases. Emerging data mining applications are important factors to drive the architecture of future microprocessors. This paper analyzes the performance scalability on parallel architectures of such applications to understand how to best architect the next generation of microprocessors that will have many CPU cores on chip.
Jan
5
Posted by coder.
Simon Fell > Its just code > Share and Enjoy
a completely new SOAP stack … was written from the ground up purely to be Salesforces server side soap processor, its is extensible just enough to do its job and no more (many soap tools are extremely extensible, and it comes at a considerable cost), we concentrated hard on perf both response time and scalability. The open source soap stack that we used previously has particularly bad scalability issues, …
Jan
4
Posted by Coder.
Jon Masamitsu’s Weblog
Ergomonics has a default for the relative sizes of the young generation and the tenured generation in the heap. If you have command line flags to specify the sizes of the generations (probably something like -XX:NewRatio=ratio or -XX:MaxNewSize=bytes), use them. GC ergonomics normally does not change the maximum size of a generation so if you know something about how your application runs such that you know it benefits from a larger or smaller young generation, pass …
Dec
29
Posted by Coder.
Weblogs Forum – Java API Design Guidelines
Design to evolve.
Correctness, then simplicity, then efficiency.
Interfaces are overvalued.
Be careful with packages.
Read Effective Java.
Dec
29
Posted by Coder.
DDJ>Thoughts on Language Design
A number of people pointed out that if your language has procedure calls and block structure, and your optimizing compiler is sufficiently talented, then goto is merely a special case of a procedure call—not only theoretically, but pragmatically, and if a procedure call without arguments isn’t as fast as a goto, then your optimizing compiler is leaving a lot of performance on the table.
Dec
29
Posted by Coder.
A brief John Carmack interview from Guardian Unlimited: Gamesblog
Was it strange returning to the very origins of Doom – in terms of graphics, CPU, memory restrictions? Did it bring back any memories of your work on the original game?I’m really not the reminiscing type. Capabilities wise, everything I was able to do back then, I can do a lot better now, but the mobile platform isn’t well suited to tight optimization because of the incredible range of performance you are …
Dec
25
Posted by Coder.
Comparing Two High-Performance I/O Design Patterns
This article investigates and compares different design patterns of high performance TCP-based servers. In addition to existing approaches, it proposes a scalable single-codebase, multi-platform solution (with code examples) and describes its fine-tuning on different platforms. It also compares performance of Java, C# and C++ implementations of proposed and existing solutions.