Clonezilla / Discussion / Clonezilla live: 2.7.1-22 is 10 times slower than 2.6.1-25

Rado - 2021-05-14

I have both of the mentioned versions and for unknown reasons 2.7.1 is literally 10 times slower than 2.6.1 - regardless of whethere it's being loaded to RAM or directly from the USB stick.
Everywhere where the program has to detect available partitions, 2.6.1 displays them instantly whereas 2.7.1 thinks about 10 seconds or longer. For instance, the window with yellow letters where it reads "Press Ctrl+C to exit this window" - that window appears instantly in 2.6.1 whereas in 2.7.1 it takes 10-15 seconds to appear. It's the same with all other windows where partition detection is happening.
I'm gonna use 2.6.1 for now but I thought you should know about that performance problem.
Also, it would be a good idea detection of RAID partitions to happen only once at the beginning, not every time partition detection happens. It's logical that if the program doesn't find any RAID partitions at the beginning, then there are none.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeremy Boden - 2021-05-14

If you are cloning a disk, I spend longer than 10 seconds checking that I'm backing up the right thing to the right place!

More haste is less speed?
Performance only matters during the actual cloning.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Rado - 2021-05-15
  
  No, not cloning a whole disk. Just a partition. Besides, I wasn't talking about the compression itself, I was talking about the process BEFORE compression, where Clonezilla first detects available and non-busy partitions:
  https://www.mightygamesmag.de/wp-content/uploads/2016/07/CloneD11.png
  On 2.6.1 this window appears instantly, whereas on 2.7.1 Clonezilla "thinks" at least 10 seconds before this window appears.
  Before you start the compression there's another screen with black background where Clonezilla detects available partitions again and 2.7.1 takes too long there bc it seems it's checking for RAID partitions among the regular partition detection. For unknown reasons that check takes a lot of time. That's why I said it would be a good idea to make Clonezilla check for RAID partitions just once at the very beginning of the program.
  
  The compression itself is perfect, if you know which Z-option to use. I use z9p. With z9p more haste = more speed. 23 GB compressed to 6.6 GB in a little longer than a minute and decompressed in less than 30 seconds.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Steven Shiau - 2021-05-16
    
    "Clonezilla detects available partitions again and 2.7.1 takes too long there bc it seems it's checking for RAID partitions among the regular partition detection. For unknown reasons that check takes a lot of time." -> It should take only several secs if you do not have many maybe partitions... Since it uses lsblk to get the type and it will give results in very short time if there is no issues. I suspect that if you change to use other version of Clonezilla live, e.g, 2.7.2-30 or 20210511-hirsute, the results should be different.
    
    Steven
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Rado - 2021-05-17
      
      Like I said, this long time to detect happens only in 2.7.1. In 2.6.1 detection happens in less than 1 second. The number of partitions is just 4. Or 5, if you count Ventoy's partition on the USB stick.
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - Steven Shiau - 2021-05-17
        
        So you meant you have tried Clonezilla live 2.7.2-30 or 20210511-hirsute, and there is no such issue?
        
        Steven
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Alan Sterger - 2021-05-14

I saw 10 Gbit/min hit as well. Staying on the faster clonezilla-live-20200910-groovy-amd64.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

yellowsoar - 2021-10-04

I tried on a CJS laptop with Ventoy:
clonezilla-live-2.6.1-25-amd64 => 1-2 secs (sometimes in a flash)
clonezilla-live-2.7.3-19-amd64 => 7-9 secs
And it took longer for a PC with Gigabyte Z370M D3H mainboard for 2.7.3-19-amd64,
I'll say up to 12-15 secs... (Thats's why I'm here XDDD)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2021-10-04

How about testing Clonezilla live 2.8.0-9? Any improvements?
https://clonezilla.org/downloads.php

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- yellowsoar - 2021-10-04
  
  Well...
  First scan took 5-6 secs and 4 secs for the periodical scan.
  But I found something...
  After the detection (ctrl + c), cancel everything and back to the choose mode menu.
  Than choose the rerun1(start over) option and start clonezilla again...
  It's almost as fast as clonezilla-live-2.6.1-25-amd64.
  
  Last edit: yellowsoar 2021-10-04
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2021-10-06

Please give testing Clonezilla live >= 2.8.0-12 a try:
https://clonezilla.org/downloads.php
We have improved the mechanism to search the disks and partitions. It should run faster.
Please let us know the results.
Thanks.

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- yellowsoar - 2021-10-07
  
  Hmmm....bad news first! :p
  Start Clonezilla in non-RAM mode will get empty device list.
  And the good news is...
  It's now even faster than clonezilla-live-2.6.1-25-amd64 for scanning stage.
  But only in RAM mode! XDDD
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Could you please boot Clonezilla live in"non-RAM mode", then run;

sudo -i
cat /proc/partitions
blkid
parted -s /dev/sda print
parted -s /dev/sdb print
... Please run all of the disks you have using the command parted.
Then post the results of 2-4.
Thanks.

Steven

Step2

major minor  #blocks  name

 259        0  250059096 nvme0n1
 259        1     510976 nvme0n1p1
 259        2     102400 nvme0n1p2
 259        3      16384 nvme0n1p3
 259        4  233082916 nvme0n1p4
 259        5     628736 nvme0n1p5
   8        0   30283008 sda
   8        1   30249216 sda1
   8        2      32768 sda2
   8       16  234431064 sdb
   8       17      16367 sdb1
   8       18  234413056 sdb2
 254        0     328704 dm-0
   7        0     270796 loop0

Step3

/dev/loop0: TYPE="squashfs"
/dev/nvme0n1p5: BLOCK_SIZE="512" UUID="CE5EF7D15EF7AFF7" TYPE="ntfs" PARTUUID="bc4aa511-ad74-43c0-ab37-8c6d1c10ae31"
/dev/nvme0n1p1: LABEL="M-dM-?M-.M-eM->M-)" BLOCK_SIZE="512" UUID="E284562C84560407" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="6f6a8047-82e0-4f1c-91f0-05f3869872e9"
/dev/nvme0n1p4: BLOCK_SIZE="512" UUID="2AC2591CC258ED97" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a9e52d1f-d5fd-4178-b8bc-8b1e3f6f673d"
/dev/nvme0n1p2: UUID="FA56-7389" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9641ceb6-bfa7-4356-a489-e4397d03d7db"
/dev/sdb2: LABEL="temp" UUID="32D1-40F7" BLOCK_SIZE="512" TYPE="exfat" PARTLABEL="Basic data partition" PARTUUID="2caf2e30-a866-4aa8-8afe-d1a15528f2e5"
/dev/dm-0: BLOCK_SIZE="2048" UUID="2021-10-06-02-04-07-00" LABEL="2.8.0-12-amd64" TYPE="iso9660" PTUUID="598178e7" PTTYPE="dos"
/dev/sda1: LABEL="Ventoy" UUID="4E21-0000" BLOCK_SIZE="512" TYPE="exfat" PTTYPE="dos" PARTUUID="6ee14175-01"
/dev/nvme0n1p3: PARTLABEL="Microsoft reserved partition" PARTUUID="9578a8e0-cdc3-42d9-92e1-57a0743c4cb0"
/dev/sdb1: PARTLABEL="Microsoft reserved partition" PARTUUID="bb228dae-1971-481e-9617-1364a26ef6f6"

and lsblk

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0 264.4M  1 loop /usr/lib/live/mount/rootfs/filesystem.squashfs
                                      /run/live/rootfs/filesystem.squashfs
sda           8:0    1  28.9G  0 disk 
├─sda1        8:1    1  28.8G  0 part 
└─sda2        8:2    1    32M  0 part 
sdb           8:16   0 223.6G  0 disk 
├─sdb1        8:17   0    16M  0 part 
└─sdb2        8:18   0 223.6G  0 part /mnt/usb
nvme0n1     259:0    0 238.5G  0 disk 
├─nvme0n1p1 259:1    0   499M  0 part 
├─nvme0n1p2 259:2    0   100M  0 part 
├─nvme0n1p3 259:3    0    16M  0 part 
├─nvme0n1p4 259:4    0 222.3G  0 part 
└─nvme0n1p5 259:5    0   614M  0 part

Step4

/dev/sda

Model:  USB DISK 2.0 (scsi)
Disk /dev/sda: 31.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  31.0GB  31.0GB  primary               boot
 2      31.0GB  31.0GB  33.6MB  primary  fat16        esp

/dev/sdb

Model: ATA INTEL SSDSC2KW24 (scsi)
Disk /dev/sdb: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      17.4kB  16.8MB  16.8MB               Microsoft reserved partition  msftres
 2      16.8MB  240GB   240GB                Basic data partition          msftdata

/dev/nvme0n1

Model: SAMSUNG MZVLW256HEHP-00000 (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  524MB  523MB   ntfs         Basic data partition          hidden, diag
 2      524MB   629MB  105MB   fat32        EFI system partition          boot, esp
 3      629MB   646MB  16.8MB               Microsoft reserved partition  msftres
 4      646MB   239GB  239GB   ntfs         Basic data partition          msftdata
 5      255GB   256GB  644MB   ntfs                                       hidden, diag

Steven Shiau - 2021-10-07

OK, thanks. I need more:

sfdisk -d /dev/sda > sda.pt

sfdisk -d /dev/sdb > sdb.pt

sfdisk -d /dev/nvme0n1 > nvme0n1.pt
Please attach the files sda.pt, sdb.pt, nvme0n1.pt. With that files, I will try to reproduce this issue here.
BTW, when you mentioned " Start Clonezilla in non-RAM mode will get empty device list.", could you please take photos about the screen then post them, too?
Thank you very much.

Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- yellowsoar - 2021-10-07
  
  Here it is.
  Can't post attachments without content on SourceForge. XDDD
  
  Last edit: yellowsoar 2021-10-07
  
  nvme0n1.pt
  
  p1.png
  
  p2.png
  
  sda.pt
  
  sdb.pt
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2021-10-07

Somehow I can not reproduce this issue here.
If you are familiar with screen or tmux, could you please boot Clonezilla live 2.8.0-12 in"non-RAM mode", then run;

sudo -i

screen

rm -rf /tmp/ocs-cache/

bash -x ocs-scan-disk
Then copy & paste the output of (4), and attach it.
Thanks.

Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- yellowsoar - 2021-10-07
  
  I save it by capture-pane and save-buffer function in tmux.
  
  ouput.txt
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2021-10-08

OK, thanks for providing the info.
We have fixed this issue, and uploaded Clonezilla live 2.8.0-16 and 20211008-*:
https://clonezilla.org/downloads.php
Please it a try, and let us know the results.
Thanks.

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- yellowsoar - 2021-10-08
  
  I test clonezilla-live-2.8.0-16-amd64 for both RAM and non-RAM mode.
  The "empty device list" issue is now solved!
  And for the performance issue...
  It take 2-3 secs now but sometimes up to 3-4 secs for the first round.
  Anyway...it's better than "10 times slower" before.
  So... I guess it's now case closed?! Cheers~
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2021-10-08

Thanks for confirming that.
Yes, some steps can not be neglected, so they are added again. Hence it takes a few more time to run for the 1st time. Once the cache files are created, later runs will be faster.

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

2.7.1-22 is 10 times slower than 2.6.1-25

A partition and disk imaging/cloning program

Forums

Help

2.7.1-22 is 10 times slower than 2.6.1-25

Step2

Step3

Step4

/dev/sda

/dev/sdb

/dev/nvme0n1

2.7.1-22 is 10 times slower than 2.6.1-25

A partition and disk imaging/cloning program

Forums

Help

2.7.1-22 is 10 times slower than 2.6.1-25 document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

Step2

Step3

Step4

/dev/sda

/dev/sdb

/dev/nvme0n1

2.7.1-22 is 10 times slower than 2.6.1-25