Alex,
I was looking at the workload file for reverse mode proxy testing -- webaxe.pg, and had some concerns about capacity testing. It looks like the script is supposed to work the "polymix-2" way, where each client and server gets a single IP address, as opposed to the "polymix-3" way, where each client and server gets a range of IP addresses, allocated via the aka utility.
Do you have any comment on whether or not we can go ahead and use client aliases for the webaxe workload instead of individual IP's? And how do we get around the fact that in reverse mode, only a single web server is being cached? Should we just set up our cache to cache a range of web server IP's to accomodate the test? It seems that the key limitation here is that we're now talking about a single web server address, although almost 100% of the content, under the right circumstances, is designed to be cacheable, so I can see how a single server could probably handle a significant load. I understood that there had to be one client to each server though, and that doesn't make sense for this kind of testing, IMO.
I haven't looked at this very much yet, but I was hoping I could get these questions answered before I started investing time into setting up a test.
Thanks in advance,
-Joe-
This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:16 MDT