DJHell .'s Library tagged performance → View Popular

Filter:
All
Annotated

25 Nov 09

Java Tuning White Paper

java.sun.com/...tuning.html - Preview

java performance tuning Garbage Collection

The initial target for this tuning document is tuning
server applications on large, multi-processor servers.
Why are there "Tuning Ideas" and not just blanket recommendations?
Because every application is different and no one set of recommendations
is right for every deployment environment. The Tuning Ideas
section is intended to give you not just Java command line options
but also background on what they mean and when they may lead
to increased performance.
5 more annotations...
- By gathering detailed data on actual application
  performance you can fine tune command line options and have
  an idea where to focus coding improvement efforts.
- Before you begin tuning or consider application level changes
  to take advantage of new language features it is still worthwhile
  to upgrade to the latest major Java™ release.
- Update releases often include bug fixes and performance improvements.
  By deploying the most recent update release for Java™ you will benefit from
  the latest and greatest performance improvements.
- Even though Java is cross platform it does rely on the underlying
  operating system and therefore it is important that the OS basis for
  the Java™ Platform is as up-to-date as possible
- Be aware that various system activities and the operations of other
  applications running on your system can introduce significant variance
  into the measurements of any application's performance, including Java
  applications. The activities of the OS and other applications may
  introduce CPU, Memory, disk or network resource contention
  that may interfere with your measurements.
  
  Before you begin to measure Java performance try to assess application
  behavior that may discolor your performance results (e.g.
  accessing the Internet for updates, reading files from the users home
  directory, etc.). By simplifying application behavior as much as possible
  and by changing only one variable at a time (i.e. operating system
  tunable parameter, Java command line option, application argument, etc.)
  your performance investigation can track the impact of each change
  independently.

21 Jun 09

MySQL Performance Blog

www.mysqlperformanceblog.com/ - Preview

MySQL Performance Linux Open Source Blog databases

08 Jun 09

Performanceprobleme? Datenzugriff nicht vergessen || IT-Republik - JAXenter - Artikel

it-republik.de/...riff-nicht-vergessen-2247.html - Preview

JaxEnter performance orm persistence databases articles

05 Jun 09

Page Speed Home

Page Speed is an open-source Firefox/Firebug Add-on. Webmasters and web developers can use Page Speed to evaluate the performance of their web pages and to get suggestions on how to improve them.

code.google.com/...index.html - Preview

Google Page Speed Open Source Firefox Firebug extensions web performance

25 May 09

Best Practices for Speeding Up Your Web Site

developer.yahoo.com/...rules.html - Preview

Internet Leistung Web Yahoo! performance web development

If your server is Apache, use the ExpiresDefault directive to set an expiration date relative to the current date.
ExpiresDefault "access plus 10 years"
5 more annotations...
- if you use a far future Expires header you have to change the component's filename whenever the component changes
- The problem with ETags is that they typically are constructed using attributes that make them unique to a specific server hosting a site. ETags won't match when a browser gets the original component from one server and later tries to validate that component on a different server, a situation that is all too common on Web sites that use a cluster of servers to handle requests. By default, both Apache and IIS embed data in the ETag that dramatically reduces the odds of the validity test succeeding on web sites with multiple servers.
  The ETag format for Apache 1.3 and 2.x is inode-size-timestamp. Although a given file may reside in the same directory across multiple servers, and have the same file size, permissions, timestamp, etc., its inode is different from one server to the next.
- The end result is ETags generated by Apache and IIS for the exact same component won't match from one server to another. If the ETags don't match, the user doesn't receive the small, fast 304 response that ETags were designed for; instead, they'll get a normal 200 response along with all the data for the component.
- If you're not taking advantage of the flexible validation model that ETags provide, it's better to just remove the ETag altogether. The Last-Modified header validates based on the component's timestamp. And removing the ETag reduces the size of the HTTP headers in both the response and subsequent requests.
- FileETag none