Opened 10 years ago

Closed 10 years ago

#4167 closed Bug (worksforme)

2.30b1 checks slowly

Reported by: Frex Owned by:
Priority: Normal Milestone: None Set
Component: Daemon Version: 2.22+
Severity: Normal Keywords:
Cc:

Description

Checking the same torrent with 2.30b1 gets me an average checking speed of 7-8 MiB/s. After replacing the daemon binary with the one from r12242, it easily goes up to 60 MiB/s, and never under 40 MiB/s.

This is on a dual-core AMD64 running 64-bit Squeeze with ext4 formatted SATA disks, and 2 GB RAM.

Change History (3)

comment:1 Changed 10 years ago by jordan

I'm not seeing any significant speed difference between 2.21 and 2.30b1 wrt "Verify local data". I ran three verify passes on each version and got these results:

2.30b1:

  • Verification is done. It took 33 seconds to verify 1842840864 bytes (54201201 bytes per second)
  • Verification is done. It took 31 seconds to verify 1842840864 bytes (57588777 bytes per second)
  • Verification is done. It took 31 seconds to verify 1842840864 bytes (57588777 bytes per second)

2.21:

  • Verification is done. It took 31 seconds to verify 1842840864 bytes (57588777 bytes per second)
  • Verification is done. It took 30 seconds to verify 1842840864 bytes (59446479 bytes per second)
  • Verification is done. It took 31 seconds to verify 1842840864 bytes (57588777 bytes per second)

Do you have any suggestions on how I should trigger the verify speed difference that you're reporting?

comment:2 Changed 10 years ago by Frex

I just set up a clean environment to run some tests, and my results are the same as yours :|

The day I opened this ticket, I remember opening one of the .resume files in a hexviewer with the daemon still running. Then I stopped the daemon for some maintenance and when it came back up, all the torrents were at 0%: the .resume files were gone, so I paused all and begun the check.

20 mins later, I checked again and noticed it was well behind schedule. iotop/top showed transmission-daemon was the only process actually using the system; I tried a few things and as soon as I replaced the daemon everything went back to normal.

Now I'm trying to reproduce the same conditions, will let you know.

comment:3 Changed 10 years ago by jordan

  • Resolution set to worksforme
  • Status changed from new to closed

Please reopen this ticket with more information. Thank you!

Note: See TracTickets for help on using tickets.