> However, I am not sure I can agree with your "minimum cycle"
> analysis. It seems to me that since the object birthday is selected at
> random, even objects with 2 year cycle (olcStatic) can be modified
> during a short test:
Right. I realized this after I sent the message.
> I think that PolyMix content type-based life cycle settings
> are reasonable. Ideally, we need to add a few "hot" servers with
> content that does not follow "normal" or "average" life cycle
> patterns. Call them CNN servers if you wish. Once those servers are
> introduced into the mix, they should receive significantly more
> traffic that an average server and have frequent content
> modifications, at least for index.html-like objects (images on cnn.com
> do not change often if at all, I guess).
Ok. This sounds good.
> Both features (skewed origin server access pattern and
> frequent content modification) are already supported. You can improve
> your PolyMix workload by using them. Hopefully, we can add hot servers
> to PolyMix-5. The difficulty is in automatic spreading the hot server
> agents among available simulation hosts (PCs) so that no single host
> gets overloaded.
Do you have any suggestions for parameters values (e.g. what fraction
of the requests should go to the hot servers)?
> The out-of-sync problems you pointed out are now fixed. Please
> let me know if I missed anything.
Looks good. Thanks.
-- public key: finger mukesh@cs.cmu.edu fingerprint: BDAB AB7A ADFB 9229 1BD8 45FD BE21 850C E36C D4AA
This archive was generated by hypermail 2b29 : Mon Feb 06 2006 - 12:00:22 MST