I have two laptops, I’ll call them laptop 1 and laptop 2.

Laptop 1 is my gaming laptop, and laptop 2 is a very low-spec one that I use as a jellyfin server. Here’s the neofetch result for both of them:

Laptop 1

Laptop 2

The problem

On both of them, I copied a 5GB folder from the laptop to my 3.0 usb flash drive, I used this rsync command on each:

rsync -a --progress folder_path destination_folder_path

Laptop Average transfer speed
Laptop 1 9MB/s
Laptop 2 45MB/s

How is this possible? The Laptop 1 is way superior than laptop 2. The laptop 1 has an nvme SSD while laptop 2 has an old 320GB HDD, yet the transfer speed difference is insane.

Does KDE affect the folder copying somehow? If I copy a file on the same SSD on laptop 1, the speed reaches more than 400MB/s.

What is going on here?

    • federino@programming.devOP
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      4 months ago

      I’m not using a USB hub. How can I confirm that the usb port is indeed a 3.0 one? Is the color blue of the port enough?

      • AnUnusualRelic@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        edit-2
        4 months ago

        It’s hard to be completely sure with USB. I think if you can identify the controller, you should be reasonably sure it’s actually USB 3 (but then you’ve got the various flavours of USB 3).

        You can browse the output of lspci which should tell you the capabilities of your controllers. In theory.

        • Longpork3@lemmy.nz
          link
          fedilink
          arrow-up
          1
          ·
          4 months ago

          Am easy option is to check the output of lsusb and check which bus the storage device shows up on. Device 1 on each bus is the controller which will show as usb1/2/3, with every other device on that bus running at that speed.

  • MentalEdge
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    4 months ago

    No.

    Why would the DE impact what rsync is doing?

    The speed of file transfer operations can be affected by a variety of things, CPU load, storage device load, temperature, file system, device protocol (USB/PCIE/SATA).

    • federino@programming.devOP
      link
      fedilink
      arrow-up
      2
      ·
      4 months ago

      I see. I read briefly about baloo and other kde related things and just started assuming anything I could to try and fix my problem.

      But you’re right, KDE should not affect anything about a file transfer, I’ll try posting somewhere else later and remove KDE from my line of thought.

      Thanks.

      • MentalEdge
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        4 months ago

        Oh yeah, Baloo can do wierd things. Shouldn’t be related tho.

        I’m down to help. You should investigate whether the USB standard being used is different, though both those speeds should be possible whether it’s usb 3 or 2.

        I assume the difference is consistent? Same files, same drive, same thing every time?

        What’s it rated for? If you use something like hdparm to benchmark it on each laptop, are the results wildly different?

        The gnome disks tool also has drive benchmarking if you prefer a GUI.

          • some_guy@lemmy.sdf.org
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            4 months ago

            You could try copying the same data under different circumstances.

            How about to another location on the same disk? How about to a location over the network via wifi? If possible, the same test over a wired connection? If you have a flash reader and a card, try that too?

            These will help rule in or out USB as a contributing factor.

            Edit: further, you could boot to a live image to isolate whether it’s a software issue or a configuration issue vs hardware.

  • hperrin@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    4 months ago

    It’s almost definitely not KDE. But we can’t know what it is with the information you’ve given us. We can speculate, and that’s about it.

    • c10l@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      4 months ago

      Speculating is great for troubleshooting. Every time someone speculates a possible cause, it’s possible to devise a way to test it. It’s called hypothesising. Each tested hypothesis, regardless of the actual results, helps to further the understanding of the problem.