For charts and logging we'll accept your proposals. Thanks you for your feedback!
For TCP settings we'd like to avoid any kind of registry tricks b/c of the multiple reasons: they change frequently, some of them require reboot, some are obsolete etc.
Delayes start is required as we need to be Windows Server 2003 compatible and we rely on some of the network stack components to start before we can go.
DavidMcKnight wrote:Here's a couple comments for Starwind's GUI.
I've been having a real problem with the performance of my datastores. So I hoped I could use the new performance data tools in Starwind to help. First, and I think it's already been mentioned, the "Total Bandwidth" chart needs better labels and I don't understand the numbers "Latest 0,01" what is a "0,01" value? But I what I really need is real time values. When I'm troubleshooting/testing I need to know what is going on right now. For numbers that have a "Per Second" value how about an option for the chart to update once a second. Also what's missing is the data that helps me figure out where the bottle neck is. I treat my datastores like race cars. I try to squeeze everything I can out of them. So I'm constantly tweaking them. But, from inside of Starwind, I can't tell what component (network, hard drives, CPU, etc.) needs tweaking the most.
Also when I click on a target and then my iSCSI Sessions. As I understand it, and iSCSI session is negotiated. So if I click on a particular session I could get to details for that session (Initial R2T, Firsr Burst Length, Max Burst Length, etc.). So I could make sure I have the clients and servers are configured correctly. I can never have too much information. I'd like to see all the session settings the client (VMware Host) wanted to have, all the settings Starwind wanted to use, and what settings were agreed upon.
There are several threads in the forums describing how to get a little bit more from Starwind (GlobalMaxTcpWindowSize, TcpWindowSize, Tcp1323Opts, SackOpts, etc.). Most involve digging around in the registry . There really should be a way to apply those setting from inside of Starwind's GUI.
Lastly, I'm curious, the Starwind Service it's self. I see it's set to Delayed Start. Why is that? I mean, when I start up my iSCSI Server, I want it up and running right away. I find myself rebooting the server, for whatever reason, then once I can logon, I got to services and start the service myself, not wanting to wait 2 or 3 minutes for the service to start as it is currently configured. So why is it set to delayed, what exactly is it waiting on?