Re: X over ethernet is too much slow...
On Monday, 16 December 2002 at 2:30:15 +0100, Raphal Ding wrote: One common problem is when your NIC is set to half-duplex operation and everything else is set to full duplex. I've done an ifconfig as mentioned in the handbook, and it says that my card (rl0) : media: Ethernet autoselect (100baseTX full-duplex) and of course it is active. I check on the PC running Windows, and they are also configured in full duplex. So it does not seems to be that. (Well at least it seems) What does your switch say? I have a (NetBSD) box here which, for some reason, refuses to go into full duplex mode, though it claims it is in full duplex. By the way I've set net.inet.tcp.sendspace to 65536, should I reboot to make change takes effect ? No, why should you? (it is not mentioned in man sysctl, this might be obvious but I don't know) If you reboot, you'll reset the sysctls unless you also put them in /etc/sysctl.conf. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
On Monday, 16 December 2002 at 2:51:10 +0100, Raphal Ding wrote: Using compression flag on the ssh client ? No. But I've just tried. It slows down a little, but not much. I would say that pictures do not takes 2 seconds but 2.5 seconds. Well. But it's quite far from 1/4 ;) Hmm, I seem to have missed this. Are you on an open network? Or why are you encrypting? What's the processor load like when you load these images? Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
What does the CPU utilization look like on each machine ? On the server side, CPU never goes up to 3% On the client side, I don't know since I don't have top compiled on Windows (to able to execute it in X). But the computer is really fast. How much of that is the SSH process ? sshd is about 1% average, and never goes more than 2.1% How many bytes per second is traveling across the interface when you're playing your game ? I'm a newbie so I don't really know how to monitor this. If you could point me on resources to read, I would be glad, or I'll do it on freebsd-newbies. If SSH isn't eating a lot of your CPU because not a whole lot of data is being transferred, you should maybe look elsewhere for the bottleneck. Try a different color depth - maybe 16bpp or even 8bpp would speed things up. It seems that ssh has plenty of time to do it stuff. Thanks, Raphael To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
What does your switch say ? switch says 100 full. I have a (NetBSD) box here which, for some reason, refuses to go into full duplex mode, though it claims it is in full duplex. And there is no way to know about reality ? I just can't trust ifconfig ? By the way I've set net.inet.tcp.sendspace to 65536, should I reboot to make change takes effect ? No, why should you? I did not knew that those kind of system value did not need reboot. I'm quite new to FreeBSD, and the other OS I'm working on is Mac OS 9... ;) Thanks, Raphael To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
Using compression flag on the ssh client ? Hmm, I seem to have missed this. Are you on an open network ? Yes my network is open to Internet, I have an Apple Airport Station which handles my pppoe connection, with portmapping enabled. Rules of portmapping is : - we don't serve anything here (except one port), but I'll reply to ping - I let go every packet from local to internet Or why are you encrypting ? Well in fact, it is not a matter of security. Since I'm a newbie, it was just easier to configure, since it has been already configured ;) since I use also cvs, it was a good choice for me (don't need to set up a pserver). Also my network does not contains much important data, and anyway important data is backed up often. What's the processor load like when you load these images ? On the server side, sshd takes never much than 2.1% of cpu. Thanks, Raphael To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
2 thoughts on this. Using compression flag on the ssh client? processing power of either station getting overwhelmed by the bursty graphics demands. Bri - Original Message - From: Raphaël Dingé [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, December 15, 2002 2:56 PM Subject: X over ethernet is too much slow... Hi everyone, I've the following configuration : - an ASUS mini-pc with FreeBSD on it, 900 MHz, 256 MBytes, connected on an ethernet local network. - 2 PC running Windows with X server via cygwin (each with 1,4GHz Athlon CPU, 256 MBytes RAM) - All of them are connected with a 100 Mbits switch. Basically in cygwin, I connect to the FreeBSD PC (where there is loads of software) using ssh and exporting display to the PCs running Windows. This works great, but when there are pictures to load over the network, it takes a really long time to do. For example if I start rt2_demo (railroad tycoon 2 demo, available on ports), picture takes about 2 seconds to load. This is a kind of extreme test, since games usually contains nothing but pictures. given that that game is running at 640x480 which is majored (very largely) by 1000x1000, one frame will take about 4 MBytes to transfer (let's say 32bits picture), my switch is about 10 MBytes/s so I should have one picture in less than 1/3 (shoud be something like less than 1/4) of second. Since I use ssh basic configuration, I thought that this has to be something with encryption level. I've changed it to do a more simple one, but this will change absolutely nothing. So I must have a misconfigured file or something that might be related to ssh or perhaps to X bandwidth quota, or frame rate... What should I do ? Well, my question is not about that game, this is just an example ;) I can see the impact on performance running kword or opera for example. I would be glad on any tips or hints to speed up those, any help would be greatly appreciated. Thanks, Raphael To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
One common problem is when your NIC is set to half-duplex operation and everything else is set to full duplex. I've done an ifconfig as mentioned in the handbook, and it says that my card (rl0) : media: Ethernet autoselect (100baseTX full-duplex) and of course it is active. I check on the PC running Windows, and they are also configured in full duplex. So it does not seems to be that. (Well at least it seems) By the way I've set net.inet.tcp.sendspace to 65536, should I reboot to make change takes effect ? (it is not mentioned in man sysctl, this might be obvious but I don't know) Thanks, Raphael To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
Using compression flag on the ssh client ? No. But I've just tried. It slows down a little, but not much. I would say that pictures do not takes 2 seconds but 2.5 seconds. Well. But it's quite far from 1/4 ;) processing power of either station getting overwhelmed by the bursty graphics demands. Also I tried with blowfish option, but this give me absolutely the same speed than with the default 3des. But well I'm using cygwin, so perhaps it comes from here. In fact : - software server is on FreeBSD - *but* X server is on the Windows PCs I don't know how the computers deals with that, since all thing related to X are not set on the FreeBSD PC, and as far as I see, it does not need to. I was also thinking about tcp send space, since I let the default 32K for now. I've read the handbook about optimizing that but they say that : - if applications are network intensive, have to increase sendspace and rcvspace (it seems that that's my case) - if they are not to many connections, increase sendspace (that's my case) - up to 65536, have to check that remote PCs (Windows PC) support rfc1323 if I understand well but the handbook won't tell how much I should give, and I'm sure that it's might be some experience related settings, but I'm a newbie... What would be a good value ? Should I only test ? Do I need to reboot after having set those values using sysctl ? Thanks, Raphael To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
On Mon, Dec 16, 2002 at 02:51:10AM +0100, Rapha?l Ding? wrote: Using compression flag on the ssh client ? What would be a good value ? Should I only test ? Do I need to reboot after having set those values using sysctl ? I don't think that in your environment the network latency is high enough to justify modifying sendspace and recvspace from their default values. You don't have to reboot your machine for changes to them to take effect. What does the CPU utilization look like on each machine? How much of that is the SSH process? How many bytes per second is traveling across the interface when you're playing your game? If SSH isn't eating a lot of your CPU because not a whole lot of data is being transferred, you should maybe look elsewhere for the bottleneck. Try a different color depth - maybe 16bpp or even 8bpp would speed things up. Marcus Thanks, Raphael To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
I've the following configuration : - an ASUS mini-pc with FreeBSD on it, 900 MHz, 256 MBytes, connected on an ethernet local network. - 2 PC running Windows with X server via cygwin (each with 1,4GHz Athlon CPU, 256 MBytes RAM) - All of them are connected with a 100 Mbits switch. Basically in cygwin, I connect to the FreeBSD PC (where there is loads of software) using ssh and exporting display to the PCs running Windows. This works great, but when there are pictures to load over the network, it takes a really long time to do. For example if I start rt2_demo (railroad tycoon 2 demo, available on ports), picture takes about 2 seconds to load. This is a kind of extreme test, since games usually contains nothing but pictures. I've been using another configuration where I switched from ssh to a complete xdcmp system. Loading of pictures is very faster now, in rt2_demo it is quick, so in normal desktop environment it is quite perfect. I found that increasing sendspace rscvspace for tcp in sysctl.conf did not change anything, and my thought is that it's got something to be with udp/tcp. Any thoughts on what could affect X performance so much with tcp ? Did I misconfigured something ? Thanks, Raphael To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
On Sunday, Dec 15, 2002, at 21:49 US/Pacific, Raphaël Dingé wrote: I've been using another configuration where I switched from ssh to a complete xdcmp system. Loading of pictures is very faster now, in rt2_demo it is quick, so in normal desktop environment it is quite perfect. I found that increasing sendspace rscvspace for tcp in sysctl.conf did not change anything, and my thought is that it's got something to be with udp/tcp. Any thoughts on what could affect X performance so much with tcp ? Did I misconfigured something ? X is subject to bad coding. If one of the elements on your desktop is set to update, say, 100 times/second, it can seriously affect overall refresh rates. You may need to take a protocol analyzer to the link to establish what's really going on in the conversation. Hacking around in the ethernet settings isn't liable to buy you much in your scenario. KeS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X over ethernet is too much slow...
On Sunday, 15 December 2002 at 23:56:18 +0100, Raphal Ding wrote: Hi everyone, I've the following configuration : - an ASUS mini-pc with FreeBSD on it, 900 MHz, 256 MBytes, connected on an ethernet local network. - 2 PC running Windows with X server via cygwin (each with 1,4GHz Athlon CPU, 256 MBytes RAM) - All of them are connected with a 100 Mbits switch. This works great, but when there are pictures to load over the network, it takes a really long time to do. For example if I start rt2_demo (railroad tycoon 2 demo, available on ports), picture takes about 2 seconds to load. This is a kind of extreme test, since games usually contains nothing but pictures. I would be glad on any tips or hints to speed up those, any help would be greatly appreciated. One common problem is when your NIC is set to half-duplex operation and everything else is set to full duplex. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
