Hi there,
Web Polygraph 2.5.3 is available. The change log is attached.
http://polygraph.ircache.net/sources/
This release is based primarily on the feedback we received from
users preparing for the third cache-off. We concentrated on fixing the
hit ratio problems and other known errors. This release incorporates PGL
patches for version 2.5.2. Unfortunately, we did not get as many reports
as we hoped for after the 2.5.2 release. Please start using 2.5.3 as
soon as possible so that we can meet the code freeze deadline next
Monday.
This release also enables handling of misses in polypxy, allowing
polypxy to be used in proxy balancing tests and such.
Please send bug reports to polygraph-bugs at ircache.net.
Alex.
[ bcc-ed to the bakeoff list ]
------------- change log -----------------
2.5.2 -> 2.5.3
20000719
- ProxyCacheSize in polymix-3.pg should now be set to the
*total* proxy cache size, without adjusting for the number of
polyclt processes; all adjustments are now done in
polymix-3-guts.pg, without user participation (the patch
with the above functionality was posted shortly after 2.5.2
was released)
- added the clientHostCount() function to compute the number of
client hosts based on the PolyMix-3 rules (PGL)
- added client_host_count to benchPolyMix3; if not defined by
the user, its value will be computed on-the-fly in
polymix-3-guts.pg: TheBench.client_host_count will be set to
clientHostCount(TheBench)
- added the "fexit" phase to PolyMix-3; fexit increases hit
ratio to peak level while decreasing request rate; this phase
may be required for proxies that get overwhelmed by high loads
with low hit ratio; the latter were possible during "inc1"
when hit ratio was increased along with request rate, but not
"fast enough".
- adjust Robot's recurrence ratio for Reload requests (we are still
unsure what to do with IMSes)
- collect small transaction sample during the fill phase (PolyMix-3)
- polypxy can now handle misses (not yet robust in error-rich
environments)
- a Robot that did not request any private objects from a server
before WSS was frozen should try not to request new private
oids from that server; doing otherwise populates the working
set with oids that cannot be requested again in the future
(because the corresponding WSS is zero) but may consume cache
space, etc. Generating a new private oid is always the last
resort, but it should not be the second best choice.
- hot set objects may have been sometimes chosen outside of the
working set, leading to false false hits and lower hit ratio;
other objects may have been subjected to this as well
- request embedded objects during the initial server scan (not
requesting them makes Polygraph think that an embedded object
was requested before when it was not, decreasing HR)
- made polymon report Network Bandwidth usage again (untested)
- moved foreign request error reporting so that we still have
request headers to dump
- marking a freshly accepted socket as a non-blocking or
not-naggling socket may fail when poly* is overloaded; do not
exit the program but rather continue after reporting the error
- fixed two coredump-inducing bugs in the polypxy module
- aka was exiting silently when no "anonymous" options where
specified
- support the "log_dir" option to label_results
This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:14 MDT