
software
funny
web
javascript
jenkins
education
math
selenium
ontologies
requirements
ui design
java
java compiler front end
cassandra
sonar
javaone
vaadin
ubuntu
postgres
virtualbox
maven
How To Write A Dead-Simple Online Network Drive using Java & WebDAV | North Concepts
eclipse
Fixing SSD Performance Degradation, Part 2: Page 3
For IOzone the system specifications are fairly important since they affect the command line options. In particular, the amount of system memory is important because this can have a large impact on the caching effects. If the problem sizes are small enough to fit into the system or file system cache (or at least partially), it can skew the results. Comparing the results of one system where the cache effects are fairly prominent to a system where cache effects are not conspicuous, is comparing the proverbial apples to oranges. For example, if you run the same problem size on a system with 1GB of memory versus a system with 8GB you will get much different results.The Software Industry IS the Problem
Poul-Henning Kamp One score and seven years ago, Ken Thompson brought forth a new problem, conceived by thinking, and dedicated to the proposition that those who trusted computers were in deep trouble. I am, of course, talking about Thompson's Turing Award lecture, "Reflections on Trusting Trust." 2 Unless you remember this piece by heart, you might want to take a moment to read it if at all possible. The one sentence in Thompson's lecture that really, REALLY matters is: "You can't trust code that you did not totally create yourself." This statement is not a matter of politics, opinion, taste, or in any other way a value judgment; it is a fundamental law of nature, which follows directly from pure mathematics in the general vicinity of the works of Turing and Gödel. If you doubt this, please (at your convenience) read Douglas Hofstadter's classic Gödel, Escher, Bach , and when you get to the part about "Mr.Last updated Sep 7, 2007. Performance tuning your application code can be a difficult task because it requires that you obtain deep performance information about where your application code is spending its CPU cycles. Doing this within your application is nearly impossible, or at least cumbersome to maintain. For example, you could track your method response times by creating a PerformanceTuner class as follows:
Java Reference Guide | HProf
patterns
cloud
mercurial
hibernate
web frameworks
utilitarios
haskell

