sinusoidal upload and download graph


Recommended Posts

So what causes this sinusoidal upload graph? My download graphs are usually positively skewed bell curves, I don't have any examples of those. my connection is not trottled and there is no speed boost like with comcast. The peaks of these curves are maybe 30% of my maximum upload and download bandwidth. There are lots of seeds and leeches. I a not worried about the speed just want to know what technical thing causes the curves to be like this.

Untitled.jpg <-- upload graph, more interested in knowing the cause of this.

pos_skew.gif < -- download graph, it doesn't go to zero till it's done downloading. so it may stretch like this for 20 minutes but the peak only lasts 20 seconds or so.

Link to comment
Share on other sites

So you get the same download graph with well seeded torrent like a linux distro? How many seed are you connecting to, and what speeds are you getting from each seed?

As to the download graph, as you get more and more of the pieces, it might take longer to find the other pieces - so sure the speed can drop off. Upload is quite often going to fluct depending on what is being asked from you. As you finish sending piece to leech, drop off until you start sending another, etc.

How many slots are you allowing for up and down? There are lots of variables that can effect the speed over time, the more slots you allow for should level off the graphs normally.

I prob wouldn't worry too much about how the graph looks if your speeds are good overall. Grab a very well seed linux distro.. Do you max out your connection? You should for sure. I hit my download max and stay their until completed on well seeded torrents.

Link to comment
Share on other sites

Like i said, I don't care about the speeds. I am interested in what causes the graphs. You explanation for the download graph is somewhat satisfactory. but the upload graph is like that no matter how long I leave it.... I am usually connected to 5-15 peers for upload. Those graphs are for SUSE linux.

Link to comment
Share on other sites

"I am usually connected to 5-15 peers for upload."

Gives you reason right there -- you bounce from sending to one client to the next.. How is your upload going to be a flat line?

Also how many slots do you have set for upload? Do you have checked to add more slots if less then 90% of your upload setting.

Link to comment
Share on other sites

Number of slots is 50. and no i don't have that checkbox clicked. There is no speed limit enforced.

when I say 5-15 I don't mean it keeps fluctuating between 5 and 15. It's always connected to at least 5 and at most 15.

Link to comment
Share on other sites

"Number of slots is 50."

That is just a stupid number setting -- where did you get the idea to set that high of number?? Do you have like GIG up to the internet or something?

I would suggest you run through the setup wizard on utorrent, or if using a different client RTFM to find out the correct settings.

And if you don't have a speed limit set then yeah its going to bounce around on what its sending. Not setting an upload limit is a sure way to kill your pipe and make the net pretty slow for other things while doing torrents.

You should really set upload limit to a % of your upload pipe. You can start at say 80% and move it down if you notice issues with speeds of browsing while having torrents running. And your upload slots should be limited to allow a decent upload speed to each of the clients. If you send slow speeds to a client he is not going to like you and could in fact block you, etc. But you send him good speeds he will like you and prefer you for sending his parts, etc. Too many slots compared to upload speed spread your bandwidth too thin.

All that being said -- I am not sure why anyone would give a **** if their upload speed moved around? Keep in mind your talking to quite often hundreds of different boxes in the swarm, if not thousands -- as you send pieces to other clients its almost impossible to maintain a steady upload speed, it is going to bounce around. And since you don't give any scale on those graphs - for all we know that is a 2 or 3 kb fluctuation.

If you want your upload graph to be as stable as possible - then set your upload limit to % of your true available bandwidth. Do a speedtest or something to see what speed you have, check your isp bill to see what you pay for etc.. Then set that to a % you ok with and then set it use more slots if below your limit if you want a flatter graph. And for gosh sake set a realistic number of slots ;)

So examples

Here is test of speed from utorrent - says my upload is 4.3Mbps -- which sure with speedboost from comcast yeah it is but only for a few seconds. Then it drops to half that about 2Mbps.. So it says I should set my speed to like 419KBps, which is what like 78 or 80 % of my actual reported upload speed. With 8 upload slots.

post-14624-0-50758900-1331757373.jpg

But since I only really only have about 2Mbps up - I will set this to 1.5Mbps and now it says limit should be 135KBps and only 6 slots.

post-14624-0-30556500-1331757383.jpg

This leaves me room for uploading say dns queries and requests for websites, etc. If you use up your whole pipe your going to have issues browsing and doing other things on the net while torrents are running.

For 50 slots.. it shows you should have like 50Mbps up ;)

But in realit

Link to comment
Share on other sites

I am not trying to fix anything. Don't need advice here... upload bandwidth is 100mbps and i have never filled that up with any torrent. 50 is whatever was there by default after i ran the wizard last time.

My interest was in understanding why the graph is like that and not how to fix it. I thought maybe there is a reason why the isolation are so constant. As you can see the amplitude doesn't seem to change much and the wave length is almost exactly the same at any part of the wave. Why would that be?

For example, consider this graph

easset_upload_file691_22311_e.jpg

Now I know this has nothing to do with internet speeds. But this is more like a graph that I would expect.

Link to comment
Share on other sites

Here is an interesting download graph (Didn't notice this in downloads until now). On the left, there is the scale. it's utorrent so the kB/s line is the half way mark. I am not concerned with the speed and am not trying to improve it. Just interested in the reason for such constant, neat fluctuations. I paid attention to this torrent's activity. What you see on the graph is correct. As you can see, the fluctuations are over 1MB/s.

351ifif.png

Link to comment
Share on other sites

Augh, don't be stingy on the pixels! Where's the horizontal scale, my good man? :laugh: What's the grid scale?

I am not concerned with the speed and am not trying to improve it.

I totally get that. I also think the pattern is quite interesting, as I have never seen anything so neat before. Maybe your ISP is throttling your P2P speeds?

Link to comment
Share on other sites

The answer is quite simple. Next time you download something, pay attention to the download speed reported by your torrent client. You should notice that it takes anywhere from a couple of seconds to almost a minute to reach 0 kB/s. Note: the download speed I'm talking about is different than the one shown beside the file you're downloading.

Here's a graph of a torrent file I recently downloaded. The curve has a downward slope just like yours. In mathematics, a graph like this would be referred to as exponential decay (which indicates a rapid decrease in quantity).

691394797.png

Link to comment
Share on other sites

I get this when I use Usenet too. I have a 32mbps connection giving me about a 3.7 -> 3.9mb/s down. However when I first connect to start downloading the file, my speed will be somewhere around 6-7MB/s down, then after a couple seconds drops down to 3.7->4.0mb/s down. I've had it show upwards of 10mb/s down at one time. What would cause that?

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.