Windows 10 October 2018 Update rollout now paused


  1. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #1990

    Geneo said:
    Sure it does. When loading the OS's binaries into memory they have to be decompressed. That CPU cost to decompress may be insignificant compared to the storage savings and the fact that you need to read less off of disk, but it is something. It is not "nothing else".
    You do realize that a big chunk of your RAM is also compressed?
      My Computers


  2. Posts : 1,871
    W10 pro x64 20H2 Build 19042.610
       #1991

    VBF said:
    Thanks Kari - we cross-posted - see my UPDATE in the post to which you replied. I'm hearing this as "It ain't broke so don't fix it!" (a favourite philosophy of mine!)
    Seeing as how, if I disabled it, all my Macrium images would be redundant, I think I'll leave it alone.
    I'm just curious as to WHY and WHEN it got enabled!
    Why would your Macrium images be redundant? I would have thought any restore would simply bring the OS back to how it was at the time the image was made (meaning the OS would be back to being compressed again). Macrium should also correctly save the change from compressed to non compressed and vice versa in a string of differential or incremental images.
      My Computer


  3. Posts : 1,871
    W10 pro x64 20H2 Build 19042.610
       #1992

    Thought I would just try this out. It took under two minutes to run and this is the result. I'll gain a general impression over the course of today. I'm also going to continue and make a differential backup (AOMEI) that should correctly incorporate the changes. I'll be interested to see if the data transfer rate is the same which for uncompressed is around 280 to 300mb/s.

    Windows 10 October 2018 Update rollout now paused-compress-1.png

    Windows 10 October 2018 Update rollout now paused-compress-2.png

    Windows 10 October 2018 Update rollout now paused-compress-3.png

    AND A WEIRD PROBLEM ALREADY... back in a minute.
      My Computer


  4. Posts : 1,871
    W10 pro x64 20H2 Build 19042.610
       #1993

    My screen suddenly started flashing very quickly. You can the area affected in the centre of this shot which was rapidly blinking. I could scroll up and down the page and there was also a weird part blank area of screen.

    Windows 10 October 2018 Update rollout now paused-compress-4.png
      My Computer


  5. Posts : 1,871
    W10 pro x64 20H2 Build 19042.610
       #1994

    Just done a restart and differential backup. A lot has changed as can be seen in the last two file sizes. These are separated by just 30 minutes or so. Transfer rate was down, it began at around 200mb and maxed out toward the end at 260mb.

    I've no idea on the flashing screen that happened following this experiment other than to say that it has NEVER happened before. Just opened task manager (that took a second or two to open) but generally all is quiet.

    Windows 10 October 2018 Update rollout now paused-compress-5.png

    Windows 10 October 2018 Update rollout now paused-compress-6.png
      My Computer


  6. VBF
    Posts : 602
    Win 10 Pro
       #1995

    Mooly said:
    Why would your Macrium images be redundant? I would have thought any restore would simply bring the OS back to how it was at the time the image was made (meaning the OS would be back to being compressed again). Macrium should also correctly save the change from compressed to non compressed and vice versa in a string of differential or incremental images.
    You're correct of course - redundant was the wrong word to use - the images just wouldn't "reflect" (pun intended) the present state of the OS and necessitate running compactos again...my incorrect choice of words.
      My Computers


  7. Posts : 11,247
    Windows / Linux : Arch Linux
       #1996

    Hi folks

    If the backup program is taking an image of the Disk the actual data format - i.e the file system used on the Disk won't matter and it can be in any format that's readable -- you can backup Linux XFS partitions or even RAID partitions --. (Restoring RAID is a bit more complex as you have to carefully rebuild the arrays but it can be done).

    It won't matter whether OS is compressed or not if you use the stand alone backup / recovery program as it's running in its own OS (probably some sort of WINPE environment).

    Where difficulties can arise with these programs - especially for copying things like Linux boot partitions where pointers to actual disk addresses are referenced - is if smart copy is used which is generally done to speed up the whole process.

    A slower sector by sector copy will always work whatever the data format at the cost of time and space however - and when restoring non Windows images with things like Macrium you need to ensure the restore is done again sector by sector to the same physical disk or an identical copy.

    Cheers
    jimbo
      My Computer


  8. Posts : 2,935
    Windows 10 Home x64
       #1997

    I am not using any compression at all unless I am starving for free space. And now that I am talking about that I think Microsoft's trigger for enabling compactos is just CPU power, because last 5 PCs I installed v1809 on they were all compacted, but one 32GB PC I clean installed yesterday (poor 2-core Celeron processor) wasn't compacted, although it's pretty needed in this case. For my current i7-7700 cpu, winsat cpu -compression shows 889,17 MB/s while disk output (HDD) is 160 MB/s on average (seq. read/write), so maybe I should enable compactos again.
      My Computer


  9. Posts : 384
    Windows 10 Home x64
       #1998

    Wow. I've just read the last 15 or so pages of this thread and all that is going on is people demanding to have their own PoV heard or validated. Actual advice quietened.

    Arguing over semantics, also. Thought this place was a reasonable source of information, largely thanks to the staff it probably is. The rest of it is beginning to resemble the Argument Clinic or a Communal Area clique depending on the thread.
      My Computers


  10. Posts : 15,482
    Windows10
       #1999

    eLPuSHeR said:
    I am not using any compression at all unless I am starving for free space. And now that I am talking about that I think Microsoft's trigger for enabling compactos is just CPU power, because last 5 PCs I installed v1809 on they were all compacted, but one 32GB PC I clean installed yesterday (poor 2-core Celeron processor) wasn't compacted, although it's pretty needed in this case. For my current i7-7700 cpu, winsat cpu -compression shows 889,17 MB/s while disk output (HDD) is 160 MB/s on average (seq. read/write), so maybe I should enable compactos again.
    CompactOS was introduced for small drives as a wimboot replacement.

    I find it hard to believe MS have a deliberate policy to use Compact OS as a means of system performance optimisation. I think OCCAM'S RAZOR principle applies here i.e. the algorithms to decide to use CompactOS are not that good just gets it wrong. PC Technology has moved on since CompactOS was introduced and I bet the algorithms really need to be revisited.

    Also, I have heard of people having issues when trying to recover data on another pc, although it should not affect anything. I cannot verify if such is true but I prefer not to take the risk unless essential. It may well be people confusing compactos with compressed drive to be fair.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:40.
Find Us




Windows 10 Forums