With 2.1 we get tools for monitoring CPU/Mem usage, but there is one more resource which addons use - network bandwidth.
It used by SendAddonMessage and may be some other API calls cause additional network traffic too. More and more addons use addon channel to communicate and they keep spamming raid/guild channels even for ppls who don't use this addons.
So i'm interested in some tool to measure in/out bandwidth usage per addon. For example i've heard that SWStats/KLHT create big traffic during combat and I want to check how big it is.
Another thing - may be there is some sense to make addons "register" for SendAddonMessage to not receive everything which all addons send.
It surprises me how little wow uses. I used to play it at school through a putty ssh tunnel to home and it would play fine (while you couldnt even stream webradio right there)
Yeah, I use Fubar_PerformanceFu, and if memory serves, it says that the average bandwidth is about 10 KiB/s. I could be a little off, but whatever.
In any case, I'm reminded of an older MMOG that I played on a modem. For the longest time I would lag out in the middle of the field and I'd log back in, dead. I finally found out that my modem was losing the connection momentarily, so it had to go through another handshake. Once I cut back the modem speed, the handshake was far shorter. I would lag a little bit, but instead of the handshake being 15 seconds long and timing out, it was only a few seconds and I never had a really bad issue again. My connection wound up being 14.4k to avoid the long handshake. :)
It surprises me how little wow uses. I used to play it at school through a putty ssh tunnel to home and it would play fine (while you couldnt even stream webradio right there)
How did you that? putty can't forward screen output
It surprises me how little wow uses. I used to play it at school through a putty ssh tunnel to home and it would play fine (while you couldnt even stream webradio right there)
How did you that? putty can't forward screen output
That search I found unenlightening other than seeing Wikipedia's entry on it. From there I saw the X11 application reference. Is that what you were referring to? The trouble is, there's so much about secure shell that has nothing to do with playing a game over it, and all of that is useless to someone who knows a very small amount about it and what it can do.
An SSH tunnel opens a port on the local computer (which usually only accepts a connection from localhost). The data sent to this port is then sent thru the encrypted connection to the server, and the server sends the data on to the intended destination. It's like a connection-specific VPN basically. I've used them for a number of things, the biggest being getting past the firewall at work to connect to a protected web server. My employer had SSH for me, so I created a tunnel that connected me to the web server. Normally that server was only accessible from their network.
What indie was doing was likely using the tunnel to bypass a blocked port.
It surprises me how little wow uses. I used to play it at school through a putty ssh tunnel to home and it would play fine (while you couldnt even stream webradio right there)
How did you that? putty can't forward screen output
It used by SendAddonMessage and may be some other API calls cause additional network traffic too. More and more addons use addon channel to communicate and they keep spamming raid/guild channels even for ppls who don't use this addons.
So i'm interested in some tool to measure in/out bandwidth usage per addon. For example i've heard that SWStats/KLHT create big traffic during combat and I want to check how big it is.
Another thing - may be there is some sense to make addons "register" for SendAddonMessage to not receive everything which all addons send.
In any case, I'm reminded of an older MMOG that I played on a modem. For the longest time I would lag out in the middle of the field and I'd log back in, dead. I finally found out that my modem was losing the connection momentarily, so it had to go through another handshake. Once I cut back the modem speed, the handshake was far shorter. I would lag a little bit, but instead of the handshake being 15 seconds long and timing out, it was only a few seconds and I never had a really bad issue again. My connection wound up being 14.4k to avoid the long handshake. :)
How did you that? putty can't forward screen output
You have no idea what a ssh tunnel is do you?
What indie was doing was likely using the tunnel to bypass a blocked port.
I'm sorry are you referring to me?