aMule Forum
English => aMule Help => Topic started by: MalAkye79 on November 25, 2006, 01:19:43 AM
-
i just did an upload and download bandwidth test on my comp and i got...
my DL speed is 10.7 Mbps
my UL speed is 1.68 Mbps
so with that info what should i use as my bandwidth limites in my Amule preferences to get the best download speeds?
Thank you for your help.
-
As a general rule, use an upload limit of about the 80% of your upload limit, and let the download limitless. Although with such capacities, I'm not so sure that rule works fien, but it's agood start point.
Regards.
-
Originally posted by skolnick
As a general rule, use an upload limit of about the 80% of your upload limit, and let the download limitless. Although with such capacities, I'm not so sure that rule works fien, but it's agood start point.
Regards.
im sorry but i dont quite understand what you mean. please speak to me as if im a small child LOL.
-
my UL speed is 1.68 Mbps
1.68Mbps=1680Kbit/s=210KByte/s
I think your line capacity is a bit higher, thus try setting your upload limit to 210 and your download limit to 0 (means no limit).
Regards
-
Originally posted by wuischke
my UL speed is 1.68 Mbps
1.68Mbps=1680Kbit/s=210KByte/s
I think your line capacity is a bit higher, thus try setting your upload limit to 210 and your download limit to 0 (means no limit).
Regards
ok i put my upload at 210 and my download to 900. ill see how that works out. Another quick question. Does the KAD always take long to get 2 green arrows. i always start with 1 green and 1 red and then after like a half hour i get 2 green arrows. i use MAC OS X.
-
this is a pic of my settings. i figured it would help to add this
(http://i68.photobucket.com/albums/i13/bxstylez31/Picture2.png)
-
I think your slot allocation is pretty small. Try using something like 20kB/s for each slot. Also, leave 0 in download limit (IT works for me :D).
Regards.
-
Originally posted by skolnick
I think your slot allocation is pretty small. Try using something like 20kB/s for each slot. Also, leave 0 in download limit (IT works for me :D).
Regards.
cool i tried it. i will get back to you in a few hours :)
-
(http://i68.photobucket.com/albums/i13/bxstylez31/Picture1.png)
143,9 UPLOAD and only 11,0 DOWNLOAD. this is driving me crazy.
-
well downloads still seem slower then what i think i should be getting. my new post below this one shows a pic of my upload/download speeds
-
There is an issue with 2.1.3 (and 2.1.2) that limits the download speed per source to about 3k/s. You could try my most recent cvs version (see my sig) in which this issue is fixed.
P.S. I merged your new "is this upload to download speed normal (image attached)" thread with this one.
-
Originally posted by lionel77
There is an issue with 2.1.3 (and 2.1.2) that limits the download speed per source to about 3k/s. You could try my most recent cvs version (see my sig) in which this issue is fixed.
P.S. I merged your new "is this upload to download speed normal (image attached)" thread with this one.
coo thank you. so this is what i DL
Your are requesting file: /amule/aMule-Mac.CVS.2006-08-10.noDebug_UniversalBinary_TigerOnly.zip
correct?
-
ok i got this at the end of my terminal. is this bad?
Host: amule.sourceforge.net:80
URL: http://amule.sourceforge.net/lastversion
Response: 0 (Error: 3)
WARNING: Void response on stream creation
HTTP download thread ended
amule(439,0x201e200) malloc: *** Deallocation of a pointer not malloced: 0xf018175d; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
amule(439,0x201e200) malloc: *** Deallocation of a pointer not malloced: 0xf0181759; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
do i have to keep terminal open to use this program? i shut terminal and amule closed :(
-
Yes, this is bad, it's a crash. Open the file ~/Library/Application Support/aMule/amule.conf [~ is /User/yourusername] and set NewVersionCheck= to 0. This way it should not crash.
Maybe Ken or lionel know a bit more about the cause of this crash.
-
i changed it to zero saved it and then quit terminal and amule crashed :( hopefully someone can show me how to fix this so i dont have to keep terminal open to keep the cvs amule open.
-
Ok, first of all, the malloc messages are benign, so you don't have to worry about them.
Second, I don't think you can run the cvs version without the Terminal being open. I tried starting aMule with "amule --i-would-marry-my-mule &" to demonize it, but even then it is killed, when you close the Terminal window. I assume this is because it is not simply a command line executable, but instead a program within an app bundle.
So I would recommend just hiding Terminal (using command-h), so that it is out of your sight.
-
thank you very much. i will do that. so this CVS is a more stable version then the regular Downloadable version? how often do you guys update amule. its a great program by the way :)
-
Well, on my machine here, pretty much any aMule version from the past 1.5 years or so runs very stable. To some extent that is because whenever aMule does crash, I post a backtrace so someone can fix the issue. :)
Regarding the release cycles, typically what happens is that we release a bigger new version with a lot of new features (like 2.1.0) and then a bunch of bug fixes and updates with smaller improvements (like 2.1.1-2.1.3) shortly after that. Then there is often a longer delay of like 6-9 month or so and then another bigger new version is released.
For users who want to profit from new features sooner and who are willing to run slightly more experimental versions, we offer the daily CVS sources so people can compile bleeding edge builds themselves. For Mac users we provide in addition ready-to-use CVS binaries that are updated depending on how much new code has been written in the meantime and depending on how much time I have on my hands. Usually I try to release a new CVS build every 4-6 weeks or so, but the last couple month have been a little slow, because many of the devs were busy, so that I did not see the need to release a new CVS build. I will, however, probably release the next one soon.
-
you guys do a great job. i DL both versions and i will just use whichever one gives me the best download speed. i was told that the CVS had a bug fix for DL speed. so i will try that one untill a new Update comes out :)
-
You should be able to use the nohup command to get aMule to keep running after the Terminal window is closed. Something like:
nohup /Applications/aMule.app/Contents/MacOS/amule --i-would-marry-my-mule >/dev/console 2>&1 &
It's possible that just redirecting stdout and stderr and backgrounding it would be enough, and nohup is overkill. But no harm.
-
Originally posted by ken
You should be able to use the nohup command to get aMule to keep running after the Terminal window is closed. Something like:
nohup /Applications/aMule.app/Contents/MacOS/amule --i-would-marry-my-mule >/dev/console 2>&1 &
It's possible that just redirecting stdout and stderr and backgrounding it would be enough, and nohup is overkill. But no harm.
what do i type that into the terminal window?
-
Originally posted by MalAkye79
Originally posted by ken
You should be able to use the nohup command to get aMule to keep running after the Terminal window is closed. Something like:
nohup /Applications/aMule.app/Contents/MacOS/amule --i-would-marry-my-mule >/dev/console 2>&1 &
It's possible that just redirecting stdout and stderr and backgrounding it would be enough, and nohup is overkill. But no harm.
what do i type that into the terminal window?
Exactly what ken wrote above:
"nohup /Applications/aMule.app/Contents/MacOS/amule --i-would-marry-my-mule >/dev/console 2>&1 &"
(provided that your aMule application is in /Applications).