>>-perfcli-- --mkprofile--+----------------------+-- -----------> '--desc--"description"-' >--+-----------+-- --+---------------+-- -----------------------> '--io--rate-' '--trans-- size-' >--+---------------------+-- --+------------------------+-- ----> '--readcache--percent-' '--writedestage--percent-' >--+----------------+-- --+-----------------+-- ----------------> '--read--percent-' '--write--percent-' >--+-------------------+-- --+--------------------+-- ----------> '--seqread--percent-' '--seqwrite--percent-' >--+-----------------------+--+-------------------+-- ----------> '--starttime--starttime-' '--endtime--endtime-' >--+-----------------------+--+-------------------+-- ----------> '--startdate--startdate-' '--enddate--enddate-' >--+-----------------------+--profile_name--------------------->< '--timemode--+-client-+-' +-server-+ +-device-+ '-gmt----'
You can use the mkprofile command to recreate a workload profile that can later be used with the mkrecom command to create a performance recommendation for ESS volume allocation.
Profile profile_name successfully created.
An invocation example:
perfcli> mkprofile -desc "my description" -read 20 -write 25 -seqread 25 -seqwrite 30 -startdate 20040214 -starttime 08:30 -enddate 20040403 -endtime 13:00 -timemode device myprofile
The resulting output:
Profile myprofile successfully created.
In this example, the client is in the EST time zone, the server is in the PST time zone, device A is in PST, device B in is CST, the starttime is specified as 13:00, and the endtime is specified as 14:00. The timemode values are interpreted as: