I have a 5.0 environment.
I set the tool up as instructed.
I've tried running the test (after accepting the EULA) about 6-8 different times now, I never get results.
The tests run, or look to run in the console, the web page never updates, never shows correct information.
This tool does not seem ready for prime time.
hello whenever i try to start up a workload i click run now and the test starts, however i never get further than "test running (initializing vi sdk)."
any thoughts?
thanks in advance.
_charlie
Can VMware I/O Analyzer to run in multiple VMs on single host. Initial impression is that it is one appliance per host. e.g. if I want to test workloads with 2 VM appliances using different path/resources to NFS datastore to ensure maximum utiization of physical resources [i.e different vmnic,different controller etc.]
Hi All,
Not sure what I'm doing wrong...IOmeter tests run fine but when I view the results it only shows host CPU utilization stats. Can anybody help?
I just deployed the I/O Analyzer 1.5 appliance on a vSphere 4.0 host (ESX, not ESXi) version 4.0.0 build 208167 and created a configuration to test Max Throughput and had it run immediately. I tried this a couple times, rebooting the appliance in between attempts and the tests will not complete. They begin running with a status of "Running (initializing VI SDK)" and then just hang there and never error out or complete. Has anyone seen this behavior before? Any recommendations on how to fix the problem?
I have used the appliance before on a newer vSphere 5.0 test system without issues, this is the first time I have attempted to run it on 4.0, also the previous tests were run using version 1.1 of the appliance.
Thanks,
Brian
Dear Community,
We've just released I/O Analyzer 1.5.1, which includes a detailed User's Guide and most importantly patches to quite a few bugs that have been reported so far. For those who are having "test no running" issues or "scheduler is stuck in initialization state," please download and deploy the new version. Thanks those who have reported bugs and kindly provided us log files for debugging. Please let us know if you run into issues with the new release.
Thanks,
Chien-Chia on behalf of the I/O Analyzer development team
Hello,
I've got 3 hosts all connected to 3 shared 2TB datastores via iSCSI. If I want to verify the performance of each datastore, as well as the storage performance of each host, would it make sense to just have each host talk to one datastore (since they share paths) or should I test with each host hitting each datastore? I would think having multiple hosts talk to multiple datastores would make it easier to isolate host specific issues but I imagine most issues exist at a higher level than specific host issues (inadequate or misconfigured hardware vs. a bad NIC or something).
Thanks.
hello guys,
im new to this and just purchased a raid 6405 card (4 SATA WD RED 2TB Drives) in raid 5 config with 256k stripe with esxi 5.1 free edition. Is there a primer sheet where i can get what are acceptable results for my config or a general know how doc? i ran the I/O analzyer 1.5.1 on the vm where my raid card is installed and got the results below. to me the WRITES/s seem very low or am i just misinterpretting it wrong?
Introduction
In I/O Analyzer 1.5.1, we have introduced an experimental new feature, which allows users to schedule tests via HTTP commands. The idea of such an interface is to provide a mean of script-able test scheduling functionality. In this post, we briefly introduce this new interface and give a few sample use cases.
Note
Communicating with the back-end HTTP script engine
The general command to communicate with the back-end HTTP script engine is as follows:
http://<VA-IP-ADDR>:8180/IOAnalyzer/ioanalyzer/script?<...>
where <VA-IP-ADDR> is the I/O Analyzer controller VM's IP address
and <...> in the end is a subset of the following parameters, concatenated by ampersand '&' (see "supported parameter values" section below).
You may simply open a browser and type in the above URL, or you may use wget in your script/terminal to interact with the back-end script engine.
Supported parameter values
All parameter names are in lower case (case sensitive)! Parameters have no order.
Parameter Definitions (all parameters are required unless otherwise specified)
Example 1: iometer (please concatenate command in one line)
http://192.168.100.1:8180/IOAnalyzer/ioanalyzer/script?command=newtest&
name=Config-File-1&
savetofile=true&
desc=optional&
duration=300&
schedule=2013-4-20_9-0-00&
host=%3Chostname%3E,`~!@%20%23%25%26$^*()-_=+[{]}\|'%22;:/?.%3E,%3C&
host=192.168.1.1,password&
iometer=192.168.100.1,Max_IOPS.icf&
iometer=192.168.100.2,Max_IOPS.icf
Example 1 output
Parsing test: Config-File-1
Desc: optional
Duration: 300 seconds.
Scheduled time: Thu Apr 20 09:00:00 PDT 2013.
Adding host: <hostname>
Adding host: 192.168.1.1
Iometer workload added: 192.168.100.1 Max_IOPS.icf
Iometer workload added: 192.168.100.2 Max_IOPS.icf
Test in iometer mode.
Test saved.
Example 2: trace replay (please concatenate in one line)
http://192.168.100.1:8180/IOAnalyzer/ioanalyzer/script?command=newtest&
name=Config-File-2&
desc=optional&
duration=300&
schedule=2013-4-20_9-0-00&
host=192.168.1.1,password&
replay=192.168.100.1,DVDSTORE,sdb,1.0,wrap&
replay=192.168.100.2,TPCC-LIKE,sdb,1.0,ignore
Example 2 output
Parsing test: Config-File-2
Desc: optional
Duration: 300 seconds.
Scheduled time: Thu Apr 20 09:00:00 PDT 2013.
Adding host: 192.168.1.1
Replay workload added: 192.168.100.1 DVDSTORE sdb 1.0 wrap
Replay workload added: 192.168.100.2 TPCC-LIKE sdb 1.0 ignore
Test in replay mode
Example 3: listening mode
http://192.168.100.1:8180/IOAnalyzer/ioanalyzer/script?command=newtest&name=Config-File-2&duration=300&&host=192.168.1.1,password
Example 3 output
Parsing test: Config-File-2
Duration: 300 seconds.
Scheduled time: Thu Apr 20 12:56:58 PDT 2013.
Adding host: 192.168.1.1
Test in listening mode.
Report bugs
Please report bugs to io-analyzer-info (at) vmware.com.
Curious to know if you have any input on a problem in which we can successfully add the ESX hosts while in the “master” analyzer VM and the I/O Analyzer VMs are correctly listed from the ESX hosts added, but when we select the worker VMs from the drop-down in the add workload entry section nothing happens after selecting the VM and then clicking “Add”. Nothing happens after clicking the “Add” button (good, bad or otherwise).
I did some tests with the Analyzer and have some test results listed now.
I want to erase them but i cant find any way to do this.
Does anyone have an idea?
I had uploaded a remote trace file, the io analyzer notified me a successful result, but Trace characteristics display no charts:
Workload Name : exchange_loaddfdf
Trace duration is 0 Seconds
Trace contains 0 requests
Logical Block Numbers accessed in the trace ranges from to
Minimum disk size required to replay trace accurately: 0 GB
Trace contains 0% reads and 100% writes.
But, using vscsiStats -e trace_file command, I can get the trace contents:
write,2147483713,4096,1,215738104,627935733713,8207
write,2147483662,393216,96,23931272,627936635248,16392
read,2147483675,49152,12,227885808,627937646320,12178
write,2147483723,4096,1,224847424,627940438783,13619
Can anyone tell me what's the problem? Thanks.
The vscsiStats help says:
"
- trace contains NO customer sensitive data
- only information recorded is:
- serialnumber, IO block size, number of scatter-gather elements
- command type, block number, timestamp"
"
Take this trace information "write,2147483713,4096,1,215738104,627935733713,8207" as a example,
write of course this is command type
2147483713 serialnumber? what does it mean?
4096 IO block size?
1 block number?
215738104 ?
627935733713 timestamp?
8207 ?
Is there anyone could help me, thanks.
I'm currently working on validating a new vSphere 5.1 environment predicated on 10Gbit NFS.
When I'm using resxtop I can see the device statistics for the NFS volumes (CMD/s, READS/s,WRITES/s, etc.....GAVG/cmd - obviously not DAVG, KAVG or QAVG), but it appears that IO analyzer doesn't capture these, only showing me the device statistics for the local storage in each ESXi server.
Is there anyway of modifying it to display this data, or can I submit a feature request for a future release?
Thanks,
Ben
Hello,
I'm using the 1.5.1 Analyzer, I get host results but I'm not getting any VM guest results. Any ideas?
Thanks!
When run on 5.5 host it fails to start test:
Thu Oct 03 13:44:16 MSK 2013 scheduled new-config-name to run at Thu Oct 03 13:44:17 MSK 2013
Thu Oct 03 13:44:17 MSK 2013 running timer for new-config-name
Thu Oct 03 13:44:17 MSK 2013 new-config-name(iometer) is switching to run.
Thu Oct 03 13:44:17 MSK 2013 scheduled new-config-name to run at Thu Oct 03 13:44:17 MSK 2013
Thu Oct 03 13:44:17 MSK 2013 running timer for new-config-name
Thu Oct 03 13:44:17 MSK 2013 new-config-name is now running.
Thu Oct 03 13:44:17 MSK 2013 option okay...
Thu Oct 03 13:44:17 MSK 2013 StatsRepository ok...
Thu Oct 03 13:44:17 MSK 2013 jEsxtop warming up...
Thu Oct 03 13:44:17 MSK 2013 ERROR: jEsxtop init failed.
Thu Oct 03 13:44:17 MSK 2013 new-config-name has nothing to run.
If it's move to a 5.1 host it starts working again.
I am running a "Listening Mode" test in order to gather some statistics for our ESXi servers. We would like to do this over the course of a few days. Is there a way to edit the interval by which metrics are gathered? It appears to be 20 seconds. It would also be nice to modify the metrics that are captured. For example, we don't care about interrupts for this exercise. The motivation for adjusting the interval and metrics is to reduce disk space consumed by each test's data.
After pressing the Run Button in the VM iometer does not start. Look in Vm with root . Any idea?
Hello,
After working hours and hours to stress out the new storage solution Nutanix (Which i advise you to look at because it's really interesting), we found some crucial points i will sum up there :
=> In order to use a large enough file to perform IO on the whole Array, you must resize the second disk of the IOAnalyzer. The whitepaper says to delete the second disk (Used as storage by IOMeter to store the file on which IOs will really be done), using the vSphere client, and then add a new one of the wishing size. However, after that action, you will have to re initialize every workers. In order to do that, log on each worker, and use the webGui to initiate a blank run. Let it endding, and your workers will be ready. (Possible Explanation : After the deletion, the file needed by IOMeter is missing. Doing the blank run create it again.)
=> To use multiple worker, you have to execute the following steps :
=================> Log on the manager worker
=================> Use the webgui (Adding ESX, and configuring the workload)
=================> Log on the other worker VMs too
=================> Launche the stress test
=> You can use the vSphere console to control the lauching of IOmeter : Every working worker will prompt an iometer window.