News: 1617977405

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Microsoft drops 64-bit OneDrive into the pool: Windows on ARM fans need not apply. As usual

(2021/04/09)


Microsoft has [1]released a 64-bit preview of its OneDrive sync client for Windows, citing "large files" and "a lot of files" as a driver for the update.

The update has been among [2]user wishes for a while, with a 2016 whinge topping the charts ahead of arguably more useful feature requests such as syncing over a local LAN or (whisper it) a Linux client.

[3]

"Make Onedrive 64 bit! Simple as that! 32 bit Onedrive process on 64 bit OS in 2016 is simply unacceptable!" was the request and, five years later, someone deep within the dark heart of Redmond set the necessary compiler switches, tweaked the code just so ... and here we are.

Microsoft has been a little vague about the benefits of the update, pointing to those large and plentiful files as justification. "Also, 64-bit applications can access more memory than 32-bit applications (up to 18.4 million petabytes)," the company added.

[4]

We know some of Microsoft's software can be a little, er, leaky at times. But if you need 18.4 million petabytes to sync your pre-lockdown holiday snaps with Microsoft's cloud, we'd argue you have other problems on your hands.

Sadly, while the Windows client has been given the 64-bit treatment, the same largesse has not been extended to the brave souls enduring the Windows on ARM experience. Still, Omar Shahine, vice president of product for Microsoft OneDrive, [5]told the faithful "before you ask we are working on ARM" but neglected to give a date for when ARM fans could join the 64-bit party.

[6]

The update is Microsoft's latest step into a 64-bit world and, while the company is not short of legacy 32-bit apps, the direction of travel is clear. Certainly, the extra resources available to a 64-bit app are handy, even if the immediate benefits vary widely depending on what the app is doing. [7]64-bit Visual Studio, anyone? ®

Get our [8]Tech Resources



[1] https://techcommunity.microsoft.com/t5/microsoft-onedrive-blog/onedrive-sync-64-bit-for-windows-now-in-public-preview/ba-p/2260619

[2] https://onedrive.uservoice.com/forums/913522-onedrive-on-windows/suggestions/11575911-make-onedrive-64-bit

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/storage&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YHB6PzPVpzSpUDu8RAFzrAAAAFc&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/storage&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YHB6PzPVpzSpUDu8RAFzrAAAAFc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[5] https://twitter.com/OmarShahine/status/1380232054965608448

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/storage&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YHB6PzPVpzSpUDu8RAFzrAAAAFc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[7] https://ricomariani.medium.com/visual-studio-why-is-there-no-64-bit-version-yet-849abcf0e5ec

[8] https://whitepapers.theregister.com/

Does it matter?

BJC

Does it need 64 bit? It's a sync tool. It might be moving large files but it doesn't have to open them, and even if it did it doesn't need to be in one big gulp.

The Visual Studio IDE is still 32 bit. While it might not be everyone's cup of tea, it's not the fact that it's 32 bit that's the issue, is it? Horses for courses.

It really does not need to be 64bit

Abominator

A sync tool, does not need to address 64bit memory addresses.

It has no need to load the whole file in memory. A 32bit app is still able to use 64bit arithmetic for offsets points into files greater than 4GB as it sync fragments. After all the network MTU is 1500 bytes typically so a sync tool has to slice up a file for syncing.

If anything the problem these days is memory bloat with sync tools and chat applications thinking its okay to consume > 1GB of memory to run what 10 years ago took 10MB on Windows 2000 or XP.

This is people failing to understand 64bit apps are actually for memory addressing. If the sync tool needs more than 4GB or for that matter more than 50MB I would think its best to leave it well alone as its not fit for purpose as a background lightweight utility.

OneDrive? A "background lightweight utility"?

Hubert Cumberdale

Ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha.

Ha.

Ha ha.

But seriously, OneDrive is currently using nearly 2% of my six-core system and best part of a GB of RAM just ticking over. In contrast, [1]DSynchronize (which is great, by the way, if a little quirky) is using 0% and 6.7 M B [sic]. And they're realtime-syncing exactly the same files (just to different places).

[1] https://dsynchronize.en.lo4d.com/windows

mark l 2

Why are MS so poor at supporting Windows on ARM? How can you expect 3rd party developers to bother porting their apps ARM if Microsoft can't be bothered to do it for their own software.

Port to ARM

alain williams

How hard can this be ? I have been writing in C on Unix (& now Linux) systems since the mid 1980s, porting between different CPUs is not something that I give much thought to ... it just happens.

We all know Linux is great... it does infinite loops in 5 seconds.
-- Linus Torvalds