Re: Your Windows 7 Performance Index Tue Nov 03, pm heh, my computer can't even seem to complete the index test. The Windows 7 Index is useless and inaccurate. Meadows Grand Gerbil Poohbah. Jigar Maximum Gerbil. See sig Krogoth Gerbil Elder. SuperSpy Minister of Gerbil Affairs. Desktop: iK 4. Code: Select all. And different.
Log in Remember me. Register Lost your password? It's easy to post questions about Windows 11 , Windows 10 , Win8. Post anonymously or register for greater privileges. Keep it civil, please: Decorous Lounge rules strictly enforced. Contact Customer Support. Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars. AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters formerly Windows Secrets Newsletter and AskWoody Plus Alerts, emails when there are important breaking developments.
Click here for details and to sign up. Want to Advertise in the free newsletter? How about a gift subscription in honor of a birthday?
Send an email to sb askwoody. Free Newsletter Signup. I don't know if this can apply to you. Can you suggest me that how I troubleshoot this and get rid of this, how can I capture that where is the packet are being dropped?
But why this problem is win 7 only. Perhaps even call their technical support. I personally haven't done network-level debugging for this kind of issue myself, but I'd guess you'll need an analyzer or invoke some kind of trace with your existing equipment and look for differences in the traffic between Windows 7 and earlier versions.
Analysis of network protocols and 3rd party equipment are beyond my original scope with this thread I had hoped to be able to compare Windows settings to try to isolate differences. Insofar as it seems possible that my systems here might have the exact same problem if they were tied together with equipment the same as what you have, I'm not sure that would be helpful. Perhaps someone with direct experience in debugging network communications protocol problems will be willing to jump in and give you a hand.
I think we're all chasing our collected tails on this problem. This is not just a slow net issue. I upgraded one machine to windows 7 and the transfer rate from the XP file server for a mb file is about 40 second. I upgrade the second machine to windows 7 and the transfer rate from the XP file server for the same mb file is ten minutes and the whole machine gets slow and the curser jumps as it moves during file transfers. There is no effect. The NIC settings and windows services settings are identical.
My next step is a complete system reload and I thought that kind of fix was over with XP but its clear that after two years, nobody knows what this problem is all about. Forget the Network stuff, I can't even copy an.
Takes 8 days. I do graphic animations and I run after effects 5. I can render a 5GB. I score 27, on 3D mark I'll jump off a cliff 2 days. The movie file is only sec. A few KB a second. It never finishes. I can not perform backups. I can not copy files to an SD card for a camera. I cant even put more than 50MB of MP3 on a thumb drive at a time. I am SOL completely. CD takes a few min to make At least I can get it mailed out to the customer!!!!!!! Windows is the problem. The software is the culprit not hardware or ports, hubs, none of that jazz.
Regarding writing to CD, I had the same problem trying to write blu-ray discs using the Windows software, while the BD-writing software that came with the drive gets it done successfully. I reported that to Microsoft about a year ago I think, and it seemed to be just ignored. That reminds me, I need to try it with Windows 8 CP. What kind of networking do you have? Ahhhhh Win The home menu messed me all up. Ill stay with 7. It shouldn't be called Win 8. Maybe Win 7 "touch", but not Win 8.
The new versions of 8 iso releases a few weeks ago I have not played with personally, but my father in law has and his opinion was "Meh". Not much different from Dev preview. I have a standard network setup found in most homes. The transfer was wireless. I had a problem with two laptops in a network of 15 or so win7 pro client machines and a recently installed new sbs server upgraded from an old SBS server.
One of the laptops failed to consistently copy a 30mb word file to a network share on the server and gradually failed to copy anything at all, either to or from the share, and the other laptop had similar issues but intermittent. There were no problems like this before the new server was installed. What initially seemed to be a machine problem seemed to point to a network cabling issue. Where possible replaced all cables with Cat6 and eventually took the laptop to the server and connected to the same physical switch so eliminated all building cabling.
Still no good. Read this thread and tried a few of the suggestions. No good. Then set the speed of the network card in the laptop to mbps from auto. And heypresto.. The laptop was a lenovo thinkpad edge core i3 with gigabit network interface. When I first installed the server I did notice that the server failed to communicate with the old server on a mbit port of a test switch I used for the purpose of upgrading As far as my client is concerned I have fixed the problem so it will be difficult for me to test the hotfix with resetting the port back to auto.
Obviuously setting the network card speed to mbits isn't a solution but for now it keeps my client happy. It also maybe a pointer to what's going on. I followed that old thread looking for a solution to my file copy problems.
Win7 Ultimate 64bit. Tweaks didn't help. I had recently bought a couple of multi-packs of Cat6 cables and just now replaced my old cables embarrassingly enough one had a label on it "Athlon" to show its age. Did you mean you copied the file from your wife's computer instead from yours and it worked? I'm not following what was done differently from the post before.
I am experiencing this issue between an SBS server and a single Windows 7 client. Your little screengrabs are a great idea, though sadly my network settings match what you have posted and I still have very slow file access. I have around files occupying 2GB. Average speed goes between next to nothing and occasionally as fast as 1.
It can end up taking hours. I haven't applied the hotfix mentioned above and am happy enough to do so but I don't think it fits the problem; a simple copy operation across the network that should be very fast indeed.
Have you tried really basic troubleshooting stuff? Things like replacing cables, putting the systems on the same subnet, eliminating active components between the systems, etc.? I was working with a friend the other day who is wiring his house up for Ethernet, and I thought to ask him what his performance between systems is. He is having a similar issue, and he's not gotten to the bottom of it yet either, but he also uses a discrete Ethernet switch.
By contrast both cables between the server and workstation I benchmarked at the start of this thread plug directly into my router. In my case I did perform basic network trouble shooting and all succeeded. Ping is less than 1ms, no lost packets with IPv4. Now that being said my case turned out a whole lot more interesting that may help or be a red herring As the system was going bad 1st lost USB ports, then boot then hang, not boot, etc I did a quick checkdisk when I had a good boot and no problems for the Intel raid controller reported no problems.
Now I re-setup the PC with new raid arrays in the same formation on these same drives and was trying to copy back the backups to restore them which started the networking problem. Now the quirky part So I retried HDDTune with full scan, cool drive all ok but hotter drive had first few blocks ok but then fail til next 2 rows.
Ah Ha! Potentially part of page file was corrupt so windows problems in old system build and when I rebuilt the drives to be clean the copy was fine until it reached the bad blocks.
Found it, so I thought. Now the interesting part My computer parts supplier didn't have 2 new 2TB HDDs as I was going to Raid 1 them this time, but that can now wait until the other drive arrives so I only got one. So now I've got the backups restored to the 2TB and all looking good. Problem solved, but for laughs I also try again to the old MBR drive that past all the tests and it starts then stops?!?
So right now I'm in the middle of running all the full low level test on that drive again, but nothing is failing so far. If it passes I'll repartition it to GPT and try the copy again. If that works I'll report back, but has anyone else found any differences between the partition types under Win7x64 relating to the ability and speed of copying?
So after a half day performing all types of low level disk checks, the drive is reporting good so I repartition to GPT, formatted it with the defaults for NTFS and try the network copy again.
Guess what the result is? It works!?! But there is always a but now I've got the slow copy problem My setup is as follow. Cisco e as the only switch. I have 3 computers wired to, and two more over wireless. Three wired computers are 1 Windows 7 64bit, 1 OS X I just recently upgraded the Windows 7 box. New motherboard, processor, RAM. Re-installed windows, and since this, I have had the network issues. I've tried everything I could find on line, but nothing has helped copying a file from the Windows PC to another box.
Reload windows from previous build's image and update drivers for the new motherboard to see if something went wrong with my latest windows install.
That should at least tell me if it is a Windows 7 issue, or a hardware issue. Other than doing this, I have no idea what might be the problem. Sorry to leave you but I've solved my problem through network driver update, but not from the expected source. I am transferring about 50GB between some backup files and its taking forever If your data is transferring through a megabit link, then 10 megabytes per second sounds about right.
I've had the slow transfer issue with Win 7 and went looking for solutions online. I came accross the old thread started in and read that, which of course led me to this thread. My network is very simple, 1 Win 7 Desktop and 1 Win 7 laptop connected via Wifi to a broadband router. I cannot try the frame size fixes suggested as my adaptor doesn't have these options it may be possible by regediting but I have't tried that yet.
It seems to be however that fiddling with frame sizes shouldn't be needed. This test led me to the overwhelming conclusion that the culprit is the windows file sharing system itself, Samba. So to that end I started doing some deep research, investigating and network sniffing. I have now found exactly what is causing the problem. It's to do with packet clustering and timeouts. Starting from according the reasearch I found Windows Server A network optimization system was introduced by default.
This system is designed to optimize network throughput and persistance by "queuing" packets so as to send more packets in 1 burst. Windows TCP stack basically recieves a request to send a packet, the TCP stack holds this packet for a short time to see if any more packets arrive for transmission.
This allows it to send 1 big "burst" of data in 1 go rather than several smaller ones. Now this is all well and good on TCP connections as the error control and acknowledgements are handled at a deeper level. All error control has to be done by the implementing application, and THIS is where the problem arises.
When windows attempts to send a file across file sharing, it sends it via UDP, each UDP packet requires an acknowledgment from the other machine before the next packet is sent. This seriously slows down the entire process because UDP packets are being queued and not acknowleded quickly enough by the recieving machine. I am currently trying to find out how to disable this packet queuing system, which should completely eliminate the problem. I wonder why it would work on some setups and not others.
Maybe simpler networking - e. I'll be interested in hearing whether you've been able to verify that this feature is indeed the culprit, and especially whether you find a way to disable it. This is a summary output for a file transfer tool I wrote and shows XP machine 10x faster than the W7 to tranfer the same files across the same network devices to the same location. I would suggest this points to a W7 issue. The files transferred are 24 'junk'. I can supply a more detailed break down of the transfers if anyone wants them.
We have been fighting against slow network performance for several months at the office and finally nailed it down.
In other words:. Network sniffing showed packet loss, retransmissions and time-outs. We suspected every component and ran through the scenario depicted in this thread:. The problem was finally solved by Quite surprising. Not sure why but problem solved A lot of these "slow transfer" issues seem to involve some kind of non-trivial networking hardware between machines, while bridged same subnet operation seems to be more likely to be fast.
This is quite the conversation.. I have been monitoring many threads with many people affected by this. Come on MS why cant you help us poor buggers out! I admire your efforts to get this resolved, but other than asking more questions and recaping, I havent seen any concrete soltutions at all from you.
Not quite sure where you are going with all of this. You have the closest observations to what I have noted.. I am a network admin for hire in a community of , people. I have been a MS certified tech since 97 and work in the treanches each and everyday on computer issues ranging from my desktop is the wrong color to VPN connection and AD issues..
I have a hotel i have serviced since starting with NT 4 and working up thru the years to differnet server versions, differnet ws versions and all has been fine up until nov when one of the staff responsible for social media updates for the site had her XP pro computer replaced with a windows 7 pro tower.
Each user onsite has a dedicated user folder on the windows standard server onsite. Her folder has something like 50 folders in it. Perhaps a total of mb of mostly doc and excel files. Just opening her mapped drive in "my computer" results in the background of the address bar showing a green progress bar slowing going left to right over 45 seconds there abouts - just on browsing of folders!..
I even rebooted the main network switch with no fix. I read tons of documents as I am sure we all have and followed a thread which I cannot find now for the life of me!!
Two months ago I setup a net network for a church. Four computers total. One of these computers is a windows 7 pro workstation with basic file sharing tasks.
Another is the bookkeepers workstation.. Same thing with her Simple network with all hardware connected directly to new linksys E model router. Yesterday called back to a fully windows 7 home premium installation which was relocated from one building to another. Everything is the same EXCEPT a new router, patch cables and possilbe some workstations are plugged into a switch then router, instead of router then switch.
Slow simply accounting load from windows 7 home premium server to 7 home premium client. SA times out half the time. Same regisitry change on both affected computer, reboot both and its been golden. They have reported no issues in speed whatsoever.
I do believe I have this fixed as the three locations with this issue initailly is not reporting problems anymore. Hope this helps and I can recap other attempted fixes on job one if you require would have to dig to get this info however as it was a few months back and most of it didnt work!!
I was involved in a conversation prior to the creation of this thread about slow network performance. I figured I might be able to facilitate discussion on the forum that might uncover a solution, as I don't seem to suffer from the problem. I'm sorry that no perfect solution has jumped out and bit anyone yet, but you'll note I got VLCC and you to post a promising tweak in this thread!
It would be nice to hear back from others who have tried it to see if it has helped. Notably I don't have this value defined. As with many of Windows' difficulties, the system is so complex that not always does a simple fix correct everyone's problems. At least one poster above has mixed up bits and bytes, and VLCC reported this fix didn't help him as it did you.
With some luck, it may help some others. Thanks for adding your experience here! Just for reference, since your shorthand may confuse some folks, we're talking about adding the following DWORD value to the registry and setting it to I switched to Windows 7 Ultimate Sometime later I noticed my speed dropped considerably.
Not sure if it started as soon as I installed Windows 7 or later. I went through the original forum very carefully and tried many things suggested to no avail.
So I gave up for a while, until my NetGear Gb switch died. This is a nice switch and the best part of it is that it tells you what each port is seeing as far as speed. My server was a solid 1Gb for both of the Intel pro MT adapter ports. However, for the Dell workstation running Windows 7, it showed only Mbps speed which I verified when I looked at the Status page of the connection properties.
So not only was I not getting the the Gb speed when it showed 1 Gb but now the speed being negotiated was set at Mbps. I noticed that the MT on the workstation side had very old drivers and they were the only ones available at the time for it, so I purchased a ProSet Desktop Mb CT adapter which had drivers.
It was a struggle to get the Intel drivers to override the Microsoft provided ones. However, I found a way to do that. After I uninstalled the ones from microsof and trying to install the Intel version, there was an option not to install the default Microsoft ones only on windows 7 and not on windows and instead allow the install of the Intel ones.
The drivers intalled fine and I finally got the tabs provided by Intel ProSet drivers that allowed you to change the default link speed to 1Gb. I should note here that when I used the connection property advanced configuration to change to 1Gb, the connection would disappear and not show at all until you changed it back to auto negotiate.
But using the Device Manger ProSet options link speed tab to change the link speed I was able to do change the link speed. The ProSet drivers also included a utility to test the wire and the connection which finally gave me a clue.
It told me that the new Cables to Go Cat6 cable was missing 2 wires that would allow it to go to 1 Gb speed.
I changed back to the Cat5e that I already had and sure enough, I was able to set the link speed to 1Gb. So at this point I was all excited to see the old Mb file ccopy speed. At first I was really puzzled because the highest speed was 12 Mbps.
Thinking a bit about this, I got an idea to disable the internet nics I have 2 nics for each machine: 1 that goes to a Mb Switch which leads to my internet connection and my other nic which is dedicated to the internal Lan at 1Gb. When I did this the speed jumpted to approximately 30 Mbps. So amazingly, for some really stupid reason, windows chooses the slower link to copy files from one machine to another by default Anyway, so although I've found a way around the Mbps speed that the connection was being set at automatically, I'm still way slower than I want to run the connection between the computers.
I hope this helps anyone who might be having the problem of not being able to set the connection speed to 1Gb, but I'm still trying to figure out why I can't get to the very fast speeds I was used to on VISTA. I'm willing to bet that this is the work of one of the genious Microsoft updates. I'm not sure what they've done but they are being awufully quiet about it.
I'd like to make the request that folks posting here describe their actual throughput results and spell out the terms they're using clearly especially the difference between bits and bytes. It would be best to explicitly describe the file size s , how many files, and how long it takes to do what operations. For example, romelevans, what does "about mbps" or "12 Mbps" mean in your post above? What are your actual and expected file transfer rates in bytes per second and how are you actually copying those files across your network link?
As I have shown above, it should be possible, with everything working optimally, to get close to the theoretical maximum at around megabytes per second transfer rate across a 1 gigabit per second Ethernet link. Exactly how much degradation is important to this conversation, and we need to try to avoid confusion over terms.
Would like to try this with my Win 64 bit. I have the same problem with large file transfers by WiFi in Windows 7 64 bit. Looks like something is wrong not with hardware or drivers, but with network settings.
What can it be? My network system suffers from slow transfer speeds. When I first installed gigabit cards it worked well for a while, but then slowed.
Desktop system is Windows 7 Dell Core 2 Duo 2. Right now the gigabit cards are removed; just using fast Ethernet. I set the DisableBand w idthThrottling to 1 in registry. Just now I put in that registry setting on the Home Server and file transfer speed doubled!
Two windows 7 professionals, connected to a gigabit switch with cat 6 cables. Firewalls disabled. No AV software, or "internet protection" crap. Speed is not a factor while doing anything from editing huge photoshop files to loading enormous files in 3D Studio Max, and while copying data to USB devices is slower, it is not unexpectedly slower.
Given the horrifically excessive timeline of this issue, and taking into account the lack of any solution whatsoever, and seeing on a daily basis that my internet transfer speed is devastatingly faster than any internal intranet transfer, there is only one logical conclusion; Windows 7 is intended to behave this way and Microsoft has no intention of fixing it. I am extremely disgruntled over this and even more put out by the clearly deliberate ignorance by Microsoft.
I really do like Windows 7 but not being able to efficiently transfer data around my local network is SO bad that it eclipses many of the positive points that Win7 has brought to the table. I am subscribing to this thread in the vain hope that someday, somehow, I will get an email notification saying there has been a breakthrough and we can all move on from this ridiculous problem.
Please try the examples given but if you don't have the right switch then it won't matter what you do at the OS. So you're saying that switches other than these specific models can be expected to slow things down? I can believe that; without going back and scouring these threads I'm not sure we ever definitively identified anyone without a switch that was seeing a big slowdown.
For anyone following up on this thread: Please list what Ethernet switch, if any, you have between your systems. I just installed a Win7 64bit machine and had the same problems of copies across the network taking forever. So we bypassed this switch and everything copied across the network at expected speeds. However, I am trying to figure out what I can buy locally at Microcenter given I have to install this soon. The port is shared by several printers and computers. We only need an 8 port switch.
Update: Regarding the above switch I mentioned, Cisco SG D, I asked someone I know if he thought this one would work, and he said yes, that he has this exact model installed in several places and is running Windows 7. So I will give this a try and post my findings here. From my tests yesterday it certainly indicated an incompatible switch it was definitely an old model with Windows7 64bit. From the findings of this thread, it appears that the switch should be the first thing tested in terms of large data transfers - i.
I guess it makes sense; certainly the evidence is that in a number of cases the intervening network hardware e. It is quite a lot of data we're trying to transfer e. It's not too hard to imagine an implementation of a switch that just can't handle the data at full speed - though in this day and age you'd think being able to run at the full wire speed ought to be a fundamental design goal. Win7 just can't do proper file transfer Wired or wireless LAN, copying bunch of CAD files files, each about 3Mb , transfer starts ok and completely stops after files.
Wired LAN on the bench single switch etc. Just a crossover cable between a Win7 and XP machine no switch , and file transfer is still slow. XP to XP works like charm. External USB2. When one of them eventually finishes, rate of second transfer never never goes up to utilize bandwidth.
I tried bunch of different machines and OSs, but only Win7 can't perform. I agree that ethernet switches etc as any part of path need to be evaluated. Even machines using dual boot same NIC, same cable, same switch have no problem - unless running Win7.
Like everyone else I would like to see this resolved. So yes, go ahead and look elsewhere if you like, but the problem is not elsewhere, it is within Win7. In fact it did not exist until Win7 was released so if there is something incompatible, it is Win7. I have yet to find a switch that didn't have this problem. Just to be clear, have you been able to create any configurations where it runs at full wire speed without a switch as I have? Almost hard to believe that Windows 7 networking just can't work with a switch in the line, but that seems to be the implication so far in this thread!
I should think enterprise users would be raising a bigger stink if that were the case. I guess enterprise users have bigger budget and more leverage. This thread was continuation of a previous one that was closed after it grew out of proportions.
0コメント