Processor Cache Effects

Example 1: Memory accesses and performance
Example 2: Impact of cache lines
Example 3: L1 and L2 cache sizes
Example 4: Instruction-level parallelism
Example 5: Cache associativity
Example 6: False cache line sharing
Example 7: Hardware complexities


http://igoro.com/archive/gallery-of-processor-cache-effects/

Venkman JavaScript Debug

Venkman is the code name for Mozilla's JavaScript Debugger. Venkman aims to provide a powerful JavaScript debugging environment for Gecko-based browsers namely Firefox 3.x, the Netscape 7.x series of browsers, Netscape 9.x series, Mozilla Seamonkey 1.x and Mozilla Seamonkey 2.x. It does not include Gecko-based browsers such as K-Meleon 1.x, Galeon 2.x and Netscape 8.x. The debugger is available as an add-on package in XPI format. Venkman JavaScript Debugger has been provided as part of the Mozilla install distribution since October 3rd 2001.


http://www.mozilla.org/projects/venkman/

Dense = good

Applications should also take care to avoid filling the cache with data that isn't needed. Remember, the cache is very small compared to main memory and every unnecessary data byte in the cache is taking up space that could be used beneficially by more relevant data. One simple way to avoid wasting cache space is to use smaller data types when possible. For example, a data structure might include an integer numeric field that ranges in value between 1 and 1000. Often a 32-bit INT would be used to store this value, but in this case that is overkill; a SHORT (two bytes) would work as well, and take up half the space.

http://developer.amd.com/documentation/articles/pages/PerformanceOptimizationofWindowsApplicationsonAMDProcessors2.aspx.aspx
 
Tomasz Kulig