Now you can make a version that allows for not only a virtual device, but also a user assigned zwave device, and a user assigned zigbee device so we can measure hub performance, zwave network performance, and zigbee performance and see if they all take a crap at the same time or independently.
I'm mostly kidding.
I think this app is a neat idea and fully plan on trying it when I get home from business travel. No idea what it will show for me, as I haven't been having any slowdown issues, but maybe that is a useful data point too?
The speed at which Bryan puts out apps makes me think that he's cloned himself about 20 times and then forces the clones to do his bidding for him in a code sweatshop.
No idea what good is, but my data (all on virtual switch devices) looks like:
Hub1 - 0.058s
Hub2 - 0.066s
Hub3 - 0.117s
It's funny to me, as Hub1 is my most heavily loaded hub (in terms of devices, apps, and RM rules), yet it was the fastest. But like most data the absolute value probably doesn't matter as much as the trend over time.
Exactly, I think we will see a wide range of numbers but the key is do they go up over time or remain steady. I should have the driver done tonight so we can start to track data points.
It works perfectly. This is just trying it out, not a fresh boot, on a peanut plug. I think my last reboot was Saturday. I always notice the slowdown on zigbee devices first. None seen so far.
Well, that gives each individual a decent baseline of data. I would probably be looking at trends of doing this day after day, hour after hour, if I am that unstable. You could use it to bench new apps for the more intrusive apps..
Reproducibility across everyone is a whole other thing. How many apps, types of devices, etc, would come into play.
Dumb question, I suppose to create a virtual device first, then create one child with that virtual device, then if I want to test zigbee and zwave I must create one child for each?
How big of a pool do we need and then what do you want to do with it?
