Upload speeds are slow until computer is restarted


Recommended Posts

I am having a strange problem..for some reason when I go to upload something to say like mega, 1fichier, solidfiles, etc..pretty much any file host site my upload speeds only go to like 200 kb/sec but when I restart my computer and try again, my upload speed is maxed out, and regular speeds like I'm suppose to get, and I get 75 MB up..so usually its like 7.8 mb/sec and its fine for like a few hours, but then it does the same thing until I restart my computer. And when I run a speed test, that comes back fine (see below) so I don't know what is going on here. Can anyone help? and also my connection is hard wired

4648660552.png

 

I just ran another speed test at the same I was trying to upload something like you said, still getting around 200 kb/sec and speed tests are fine. and I checked in my router, there is no traffic shaping or traffic priority going on.

"75 MB up..so usually its like 7.8 mb/sec "

Well since you reversed Byte and bit here with your Big B's for bit and little b's for byte.. so are you seeing 200KByte or Kbits up because its a huge difference..

what I would like to see is a sniff when its real low and then a sniff when its working as normal.. Grab wireshark and do that.. you don't need to run it for the whole upload..  But run it for say 30 seconds on your slow upload and then 10 or so seconds on FAST upload.  PM me if you have any question on using wireshark its free and just sniff and then save the file and they might be large on your good speed upload..  But I can give you a place to upload them too so I can get them, etc.

Next time vs rebooting your computer just disable your interface and re enable it.  Are you wired or wireless?  With those speeds and that 4ms ping time I would for sure say wired, but want to make sure.  The speeds are doable with for sure with decent wireless but the ping time is really low for a wireless connection.

I'm wired directly to the router/modem. What do you want me to do exactly with wireshark? just let it run for 30 seconds with my good speed uploads, then again with the slow speed uploads?

I just tried what you said Budman..disabling it and re-enabling it(didn't know you could do that to fix a connection) and my upload speed was normal again when trying to upload something(see video I took below). Now I just gotta wait, because it's random when the upload speed at 200 kb/sec happens, so I'll post that second video when I try it again in a few hours

good upload speeds

Edited by Sharpstick68

I doubt that has anything to do with it.. But you find them in the advanced section of the driver.  Different nics, different drivers will have different options you can play with..  But I doubt its a setting like that you could tweak that is causing you a problem.

Offload is normally something you want ON!!  If your nic supports it, if doesn't and you have it on it just wouldn't do anything and still work.  What OS are you running btw?

 

 

 

driversettings.png

so has it happened again, have you taken any sniffs?  Does it happen on small files as well - what size of files are you sending.  If not too large you can just do the full sniff.  But if like 100MB then yeah the sniff would be 100MB in size ;)  Really curious to see the sniff when its bad!!

Yea it is still happening, but it is good to know that I can just disable and re-enable my network card without having to restart my computer to fix it(thanks BudMan). But it happens on files of all sizes, anywhere from 10 mb to 500 mb it's really strange. The next time it happens I will open up Wireshark and what should I look for..anything going to the file hosting site? which is solidfiles.com ?

also my network card is a Realtek® 8111E

and the network card drivers are up to date

Yeah like to see the transfer.. are you getting really all delays in the acks, is the window size not ramping up?  Are you having to retrans, etc. etc..

Kind of need to see a trace when your rocking full speed vs one when its ######.  Just because you restart your nic doesn't mean its really your end..  Maybe your sending to a different IP when its slow vs fast, etc.

 

grabbing now - but have to head to work in like 30 seconds.  Will look at today.

They are big most likely because you were downloading big files ;) 

edit:

Ok took a quick look, hope to get some more time later today.  But yeah your slow speeds make sense from the sniffs and your window size.  As you will see in the slow upload your largest size was 17462, less bytes on the wire in that frame..  While in your fast upload 62834 bytes in the frame.

Notice that in your fast upload you windows scaling is working scaled your window size by 4..  But in your slow upload scaling factor is -1?? I think this is because I missed the syn,ack for the start of this conversation so wireshark doesn't know what the scaling factor is suppose to be so just guesses.. (seeproblemwindowsizepic)  But clearly they are not the same.. So something not working in figuring out the scaling factor for the upload.  When you move large amounts of data over a wan you want a large window so you send more data in less number of packets.  So less back and forth acks while moving large amount of data.  In your slow upload your largest size is that 17k while in your fast upload your sending almost 63K bytes worth of data each time.

Now your sniffs are with 2 different file sizes or atleast showing that so not sure if you were sending the same file and just cut off the sniff or what haven't look that deep yet.  But in general if your window size is small to send say 10MB you need X number of conversations back and forth.. While each should take about the same time lets call it 30ms for example.. So if you can send that same 10MB in less interactions of send and ack, you can move that 10MB faster..

Clearly in your fast upload your sending more data per conversation then when your slow sending - huge difference between 17k and 63k.  So need to figure out why something is not working out right in your scaling?

What does this output for you?

C:\>netsh int tcp show global
Querying active state...

TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State          : enabled
Chimney Offload State               : automatic
NetDMA State                        : enabled
Direct Cache Acess (DCA)            : enabled
Receive Window Auto-Tuning Level    : normal
Add-On Congestion Control Provider  : ctcp
ECN Capability                      : enabled
RFC 1323 Timestamps                 : disabled

Can you grab a sniff from the start of your sending so I can see the syn.ack and then wireshark should be able to correctly figure out the window size for the conversation.

 

 

 

 

quicklook.png

problemwindowsize.png

Edited by BudMan

Thanks for looking over the files BudMan, really appreciate it.

I did the first command line like you asked and this is what came back

  Quote

c:\>netsh int tcp show global
Querying active state...

TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State          : enabled
Chimney Offload State               : automatic
NetDMA State                        : enabled
Direct Cache Acess (DCA)            : disabled
Receive Window Auto-Tuning Level    : normal
Add-On Congestion Control Provider  : none
ECN Capability                      : disabled
RFC 1323 Timestamps                 : disabled
** The above autotuninglevel setting is the result of Windows Scaling heuristics

overriding any local/policy configuration on at least one profile.


c:\>

 

And also here is the sniff file you asked for. I started sniffing before I even had the website up, then I tried uploading the file while it was sniffing, and these are my good speeds again, because like I said those slow upload speeds I get when attempting to upload happens at random times.. https://www.dropbox.com/s/6156l4s1cna46wo/fast-upload2.pcapng?dl=0

The good speed sniff had the syn,ack part.. What I would like to see bad speed with the syn,ack of the upload stream..

You might want to try turning these on

Add-On Congestion Control Provider  : ctcp
ECN Capability                      : enabled

netsh int tcp set global congestionprovider=ctcp

This can ramp up your window size quicker and could help in speed.  Can't hurt to turn it on.. And then do you upload tests, if you don't continue to see your good speeds or better than set it back to none.

edit: ok took a look at that next sniff and as you can see good window size sending large packets.. While your bad one was only sending 17K at the LARGEST...

decentwindowsize.thumb.png.8a1d8bbe30dd2

 

Edited by BudMan

I ran that command(as administrator) and it changed, then tried and it started out fast but then was transferring at about 2.1 MB/sec but then I closed out the site, stopped the sniff and tried again and my speeds were maxing out(you can take a look at the sniff file if you want, just let me know). But ok, I will try again some time later tonight or whenever, because like I said the slow speed is always at a random time, and I'm not uploading all the time, only when ever I feel like it, so the slow upload speeds can happen when ever..even at peak hours aka prime time 7 pm to 10/11 pm.

So if your uploading and your window size is small, then yes it will be slower if your window size is larger..  Without seeing the syn,ack of the conversation starting its impossible to see what and why they might not work out a large window size.

Ok you caught the syn so you see no windows scaling. This is why your slower is your sending smaller frames.. Remember before where you were sending 63k here your sending 17k  HUGE different for speed over a wan connection.

nowindowscaling.thumb.png.fb2e526b8ff4ed

Now just need to figure out WHY??  Let me look deeper and do some research on why windows scaling would not be used.  Did you change the option?  Also I don't like that yours has that * on it about windows scaling an heurstics - from my understanding what is reported is not always what is used..  I have to run out early this morning..  Will have more info later.

 

you enable ecn with from an elevated prompt.

C:\>netsh interface tcp set global ecncapability=enabled
Ok.

Can you show your globals again, are you still seeing the ** The above autotuninglevel setting is the result of Windows Scaling heuristics

So can you do this command

C:\>netsh interface tcp show heuristics
TCP Window Scaling heuristics Parameters
----------------------------------------------
Window Scaling heuristics         : disabled
Qualifying Destination Threshold  : 3
Profile type unknown              : normal
Profile type public               : normal
Profile type private              : normal
Profile type domain               : normal

Notice I have mine disabled..

Here you go BudMan

c:\>netsh interface tcp show heuristics
TCP Window Scaling heuristics Parameters
----------------------------------------------
Window Scaling heuristics         : enabled
Qualifying Destination Threshold  : 3
Profile type unknown              : normal
Profile type public               : normal
Profile type private              : restricted
Profile type domain               : normal


c:\>

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

    • No registered users viewing this page.
  • Posts

    • Good bit of updates, if they keep this up until the new hardware lands we could be in for some good surprises.
    • Scientists explain how bigger does not mean better for electric vehicles during colds by Sayan Sen Image by Blomst via Pixabay A new study by Cornell University researchers, working with Tompkins Consolidated Area Transit (TCAT), has found that electric buses use a lot more energy in cold weather, especially in places like Ithaca, where the roads are hilly and winters can be harsh. TCAT started testing seven battery-electric buses (BEBs) in 2021 as part of a pilot program funded by a federal grant. Over two years, the buses ran on 41 different routes in Tompkins County.However,t the buses had issues during colder months, with lower driving range and performance. To understand why, researchers looked at real-world data and developed what they called “Optimal Temperature Zone” (OTZ) models—these models show how much energy the buses would have used in ideal temperatures between 16°C and 30°C. When temperatures dropped to between −4°C and 0°C, the buses used about 48.0% more energy, including both power used to drive and energy regenerated through braking, compared to OTZ predictions. Even in the wider range of −12°C to 10°C, energy use still jumped by 28.6%. Half of this extra energy went into heating the batteries themselves. These bus batteries work best at about 24°C, so when it’s cold, they need extra power to warm up before the bus can even get moving. The other major factor was the cabin’s heating system, especially on urban routes where doors open and close often, letting in cold air. “With an all-electric vehicle, the battery is the only onboard energy source,” said Max Zhang, senior author of the study and a professor at Cornell. “Everything has to come from it.” The study also found that regenerative braking—the process that lets the battery recharge a bit while the bus slows down—didn’t work as well in cold conditions. One reason is that these bus batteries are huge, about eight times bigger than typical electric car batteries, and it’s harder to keep the temperature even across all the battery cells. To improve the buses' performance in winter, the researchers suggested a few short-term fixes: parking them indoors to keep them warmer, charging batteries while they’re still warm, and reducing the length of time the doors stay open during stops. On a bigger scale, cities might need to rethink their transit infrastructure. That includes checking how many charging stations they have, whether buses can be kept in heated garages, and how to adjust routes and schedules. “You have to try to optimize the schedule of all of the buses and to consider the capability of your infrastructure – how many charging stations you have, and if you have your own garage,” said lead author and PhD student Jintao Gu. The team found that rural routes, which have fewer stops, use less extra energy in cold weather than urban ones. That could help transit agencies decide which routes are better for electric buses during colder months. “One of the lessons we’ve learned is that these buses should be designed for the whole country, including states with colder climates,” said Zhang. “But any lessons are good lessons. This helps us learn as a society and do better.” Source: Cornell University, ScienceDirect This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act of 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing
    • Appears to be 150W PSU (Core Ultra 9) so most power delivery ports wouldn't even support it.
  • Recent Achievements

    • Dedicated
      tesla maxwell earned a badge
      Dedicated
    • Dedicated
      Camlann earned a badge
      Dedicated
    • Week One Done
      fredss earned a badge
      Week One Done
    • Dedicated
      fabioc earned a badge
      Dedicated
    • Week One Done
      GoForma earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      636
    2. 2
      Michael Scrip
      224
    3. 3
      ATLien_0
      219
    4. 4
      +FloatingFatMan
      142
    5. 5
      Xenon
      136
  • Tell a friend

    Love Neowin? Tell a friend!