If I had to take a guess, resource management is far less liberal on 32bit systems, given presumed hardware constraints the OS is challenged to work with. Perhaps Microsoft de-prioritizes background tasks(SearchIndexer, AV, metadata, etc..) in anticipation of low end systems using 32b?
Its sad 32 bit is going down the can. If this were out earlier maybe 32 bit could still be competitive.
It would be marvelous!
But Linux acceptance here is not good and there are some Windows only software that the users use like the ERP.
Could be something like that, but in Windows 10 64bit it drains the machine resources, sometimes completly
Maybe disable superfetch then.
Superfetch is a tool that preloads certain mostly used applications in memory,
so that launching those applications should go faster.
The only issue with that is that it eats allot of system memory.
We also did it.
It would be fabulous!
We also did it.
Did you analyze the GPO objects you are enforcing on those machines/users? I know that GPP printer policies at the user hive can really slow down logins in some situations.
The data Microsoft collects doesn't have any PII or business data and gives no liability to the company so that was a false flag reason to move over. Good for you, though. We were just audited two months ago, federally and state side, and we have plenty of W10 machines and didn't get so much a glance about it.
Additionally, as far as I can find through logging and traffic analysis, our Pro W10 devices don't even send out any information to MS servers.
@msmfra @msmafra Since the computer are slowing down after domain join I'd wager it's GPO side. How many GPO do you have applying? Logon scripts? Have you turned off "Computer Profiles" on GPO's that only apply user settings and vice versa?
Out IT, HR and Legal went crazy over something they found. So it must have been very serious.
Might be state or industry specific. I work in one of the most regulated industries in the US and it's not an issue with us, is all I can say. I'll send the audit team a message and see what they say though.
Hi.
There are none GPP printer policies. When using 64bit Windows 10 even machines inside OUs without ANY GPOs were (are) tremendously slow.
Hello.
Our domain is very recent 6 months and GPOs are simple divided by the three buildings in OUs for each one. Just kept, "globally", mapped drives, shortcut to the mapped drives, WMP share disable, rules for RDP connection (secure connections). Even the rule with the company wallpaper I've disabled. Most of the GPO are inside OUs.
Our Endpoint security solution (Kaspersky) is not even installed on most of the machines to help with performance.
I did a test once with a new server, fake domain and three machines without any GPO the results were the same.
I don't monitor the firewall logs but Windows 10 machines are pretty busy at network.
The greatest problem some machine become unbearable to use. Windows processes running consuming almost 100% of the RAM in the worst cases. We have here some Core 2 Duo machines. In which we did some of the first tests with the 32bit version. Was really like replacing the HDD by SDDs. The majority of our machines are Core i3 with 4Gb of RAM. Putting two identical machines side by side, one with 64bit and other with 32bit, there is really no comparison.
Hi.
I also disable most of the GPO that were ridiculous. Sector managers asking to create shortcuts to folder that were in the network share, that is already mapped with tree shortcuts, for example.
And also one mapped drive for each of the shares that the user have access to. (Why???)
Using DFS namespace and Access Based Enumeration.
You can try different windows 10 disks/distros.
Como estas no brasil é natural que seja extraida mais informação do que o normal visto que
as agencias governamentais norte americanas obrigam a ms a permitir esses tipos de acesso ilegal.
32bit is technically faster because the math is faster, 64bit just allows you to take advantage of more resources. I heard this in one of Gamers Nexus' interview of Star Citizen developers.
Q.) ...Is there anything else that you benefit from by making the conversion [64bit]?
A.) From 64bit, not that I can think of right out of the gate. It's more just support the actual space more than anything, better performance or anything. If anything it's a bit worse, but we're talking marginal difference. Yeah, if anything it's actually a tiny bit slower but with newer CPUs actually we did make a change now that the positioning work so it actually ends up being faster. But normally, if you're just gonna switch over to 64bit positioning it would a little bit slower in your math. So the only benefits we get is just sheer amount of space that it can support for the players.
-source
Anyone who understands core computing concepts knows this is a fundamentally wrong assumption. In simple terms using a '64bit OS' has no direct immediate relation to how fast 'the math' of your application is because that simply depends on what data types you use and how you use them at an application level. You can totally use 64bit data types on a 32bit machine with some impact on performance (2 mem locations) and effects on atomicity.
64bit when talking about Operating systems usually refers to memory management, addressing and to the 64bit extensions added to the x86 instruction set. It's not actually slow, in fact in many cases it is faster because the processor is able to perform operations on bigger pieces of data at a time.
Fun fact we have AMD to thank for 64bit computing we have today. The 64bit extensions Intel design (IA-64) were so bad they were all but entirely abandoned.
2 Likes
The processor itself may be able to run more efficiently when running with it's native 64-bit wordsize but that does not take into account that on Windows x86_64, 32-bit applications must run on the Windows On Windows framework. In other words, if not complied for 64-bit, 32-bit applications will run slower because of this abstraction layer between the OS and the CPU having to translate every call. A 32-bit application on a 32-bit OS will run faster than if run on a 64-bit OS, and hence 64-bit Windows OSes and the processors they run on can be thought of as being "slower" in this circumstance since the ability of the processor to perform operations on larger pieces of data at a time is not being utilized and there is extra overhead in running the application.
The Ithanium architecture was really nice actually. But no one wanted their x86 apps to run at 1/2 the speed on IA-64 processors. If compiled for IA-64, instead of x86, the applications ran much faster, far better than we get on x86_64 after normalizing for research gains. When AMD released their 64-bit processor that could run x86 apps at native speed, that was the death of IA-64. IA-64 was our gateway out of this miserable micro-instruction laden x86 architecture. AMD made millions. :- /
Might be onto something there. As a desktop user 3/4 of my steam library is 32bit .exe games. If you're running 64 bit code I can't see windows x64 being worse off but a lot of code around is still x86 based.