Feature freeze and workload beta. By May 15th, Polyteam knows and has announced all of the features that will be present in the PolyMix-3 workload. Polyteam have begun to implement these features in Polygraph. A draft (beta) specification of the PolyMix-3 workload will be distributed.

PolyMix-3 workload draft is available. Here are the included workload modifications based on the Boulder meeting decisions:

• Better popularity model/implementation, with ``hot spots'' (to be implemented)
• Shorter idle and ramp phases with at least three hours worth of reduced time (supported, but we may implement smooth ``log-based'' replacement for current ``linear'' ramps)
• Integrated fill and performance tests (partially supported, may need better ways of specifying the working set size)
• Client reloads and aborts (to be implemented)
• IMS requests and better Life Cycle model (partially supported)

A significant PolyMix-3 improvement is an integrated, constant request rate phase for filling the cache. Fill rate is specified by the vendor. At the time of writing, the upper limit for the fill rate is 100% of the peak request rate. This limit may be removed if we implement a run-time verification of how much cachable content was actually cached.

Planned Polygraph modifications that are not clearly visible in the workload file are:

• Improved run automation tools; make it easier to start, stop, and monitor a test
• Documentation
• Global configuration awareness among robots and servers
• Run-time verification of how much cachable content was actually cached
• Per-agent packet delays, loss, bandwidth limits
• Improved (more sophisticated) downtime test

Finally, here are the items with low priority that are not likely to be ready by the workload/code freeze deadlines:

• Better constant working set size (WSS) support
• Better offered BHR support
• A variety of servers and robots