From: SourceForge.net <no...@so...> - 2006-09-11 01:19:46
|
Bugs item #1396271, was opened at 2006-01-03 14:11 Message generated for change (Comment added) made by gboutwel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1396271&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Xuan Baldauf (mediumnet) Assigned to: Nobody/Anonymous (nobody) Summary: colinux-net-daemon is slow, but acceleratable Initial Comment: Hello, the TCP throughput between the colinux instance and windows networking (using colinux-net-daemon.exe or colinux-bridged-net-daemon.exe) is disappointingly slow (maybe 1MB/s) while CPU is mostly idle during network transfers. The reason might (partly) lie within Windows process scheduling. If you manage to change the scheduling priority of the particular "colinux-net-daemon.exe" process instance from "normal" to "realtime" (Windows task manager won't allow you to do this if you start coLinux as system service, but SysInternals ProcessExplorer allows this), then the TCP throughput is gaining very significantly. Therefore, to soothe this problem, coLinux should be extended to set its own scheduling priority automatically, e.g. by a command line parameter. (Maybe the priority for the network daemons should always be "realtime", because real network traffic is also handled at "realtime" priority or within interrupt handlers under most operating systems). ---------------------------------------------------------------------- >Comment By: George P Boutwell (gboutwel) Date: 2006-09-10 20:19 Message: Logged In: YES user_id=30412 As kokoko3k points out, we've had mixed reports of improves, degrades, etc on setting the proces priority. Additionally, there is a good thread on the mailing list where tweaking windows (TCP) networking parameters gave really great results. Allowing user to specify that an daemon or all of coLinux us a different priority has been asked for several times, and probably needs to be considered. But keep in mind that coLinux is a beta product AT BEST and continues to be improved. It may well reach a point where this is no longer needed. ---------------------------------------------------------------------- Comment By: andy (kokoko3k) Date: 2006-07-13 15:33 Message: Logged In: YES user_id=802927 Thanks for the hint, anyway it's not necessary to go realtime, iperf gave me 13mbps at priority normal 48mbps with priority high, same as realtime. My demon is colinux-bridget-net-daemon.exe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1396271&group_id=98788 |