| 2007-11-30 20:40:43 |
David Freitas |
description |
1) On this topic, it seems that performance is poor:
Slow internet in Gutsy compared to Windows:
http://ubuntuforums.org/showthread.php?p=3853831
2) MAJOR ISSUE:
Also, it seems that some apps fail to operate correctly because the "/proc/sys/net/ipv4/tcp_rmem" value isn't setup correctly.
The default value in Ubuntu is: "4096 87380 4194304"
The third value's recommended value is 2x the second values'. [1]
It's described here in detail.
http://cpbotha.net/2007/10/21/running-mxit-in-mpowerplayer-on-linux-ubuntu-feisty-704/
But, basically an application fails to login properly with the default tcp_rmem value in Ubuntu.
But works perfectly when setting it to
sudo sysctl net.ipv4.tcp_rmem="4096 87380 174760"
This isn't the expected value for an application that relies on TCP.
Could it be the application that is doing something wrong, or are these settings just incorrect by default in Ubuntu Feisty?
/David
-------------
References
[1] http://ubuntuforums.org/showthread.php?p=3853831 |
1) On this topic, it seems that performance is poor:
Slow internet in Gutsy compared to Windows:
http://ubuntuforums.org/showthread.php?p=3853831
2) MAJOR ISSUE:
Also, it seems that some apps fail to operate correctly because the "/proc/sys/net/ipv4/tcp_rmem" value isn't setup correctly.
The default value in Ubuntu is: "4096 87380 4194304"
The third value's recommended value is 2x the second values'. [1]
It's described here in detail.
http://cpbotha.net/2007/10/21/running-mxit-in-mpowerplayer-on-linux-ubuntu-feisty-704/
But, basically an application fails to login properly with the default tcp_rmem value in Ubuntu.
But works perfectly when setting it to
sudo sysctl net.ipv4.tcp_rmem="4096 87380 174760"
This isn't the expected value for an application that relies on TCP.
Could it be the application that is doing something wrong, or are these settings just incorrect by default in Ubuntu Feisty?
/David
-------------
References
[1] http://www.psc.edu/networking/perf_tune.html |
|
| 2008-11-16 05:05:53 |
Daniel T Chen |
procps: statusexplanation |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in procps. |
Is this symptom still reproducible in 8.10 (which uses an accepted-better TCP algorithm)? |
|
