MediSyn: A streaming media service workload generator
2004-04-29 13:56:14
À̸§ : ÀÌÁÂÇü (210.115.¢½.¢½) Á¶È¸ : 11463
MediSyn: A streaming media service workload generator
MediSyn is a streaming media service workload generator that aims to
generate long-term, realistic, reprensentative, enterprise media
service workloads. It can generate short-term media sevice
workloads as well. For details, please read our technical report
on MediSyn included in the distribution package.
Building MediSyn
Currently the code is only tested on Linux Platform.
Simply download the source code and compile the source
code on your platform.
Running MediSyn
For generating long-term trace, run shell script
medisyn.long.sh
For generating short-term trace, run shell script
medisyn.short.sh
Parameter Setting
There are a number of parameters you might want to
tune. All the tunable prarameters can be customized
through a configuration file medisyn.cfg. The thing
worth noting is that in order to generate short term
trace, the user has to specify a maximum duration of
the trace in days by setting the variable
LifespanclassTrivialClassDistParamUnifb
in the file life span section.
Output
medisyn.long.sh and medisyn.short.sh execute a
list of programs in order to generate a trace.
Each line in the shell script generates one
property. The properties are generated in the following order
each step will generate a text file with suffix .txt.
session/sessionshort executable will read the latest
.txt file which has all the properties of files
and synthesize the access log. Two logs are generated:
"session.log" and "request.log". session.log has
3 fields and in the format of
relative timestamp in seconds
file id start from 1
session duration in seconds
The file bit rate encoding and file duration properties
which can be used to populate the file set, are generated
by fileinfo executable and is written in serverinfo.txt.
request.log is quite similar to session.log, but the format
of request.log is more similar to access logs generated
by media servers such Windows Media Server Log.
request.log has 7 fields:
relative timestamp from 0 in seconds
file id start from 1
start time of the session ( currently all are 0, because
we don't support interactivity yet).
duration of the session
operation (1 means play, later we will introduce other
operations, like pause, ff, rewind)
duration of the file
bit rate of the file
user can use this log to drive the simulation without
access to serverinfo.txt.