DSM-G600, DNS-3xx and NSA-220 Hack Forum

I just wanted to let you guys know that the overly high CPU usage of v1.50 has been fixed in the development builds. Transmission now uses around 20% CPU when downloading at 700kB/s, with rare spikes to 45%.
Also, mem usage seems to have been reduced as well.

The fix has been checked into the 1.5x branch, so I assume we'll see a 1.51 bugfix release shortly.

Hi all,

I would just like to contribute a little script I wrote for updating the transmission blocklist.

Write the following in a text file:

rm [blocklist archive directory]/*
echo "Removed previous blocklist archive."
wget http://download.m0k.org/transmission/files/level1.gz -P [directory where to put the blocklist archive]
echo "Downloaded current blocklist."
gunzip -c [blocklist archive directory]/level1.gz > [blocklist archive directory]/level1.txt
echo "Expanded blocklist archive."
rm /mnt/HD_a2/.transmission-daemon/blocklists/*
echo "Refreshing transmission blocklist."
mv [blocklist archive directory]/level1.txt /mnt/HD_a2/.transmission-daemon/blocklists/
echo "Transmission blocklist refreshed."

Be sure to modify it to reflect your system. Save it then make the script executable via chmod +x blocklist_update_script.
Run the script as often as you need. I'm not sure if there is a need to restart transmission so that it would pickup the changes.

Hope this helps.

Last edited by lamski (2009-02-26 10:46:59)

craft wrote:

the latest ver. compiled from svn7949 :

http://www.dlinkhelp.eu/gex75/DNS-323-3 … 0.7949.tgz

Hey Craft,

I appreciate the nightly builds compiled for the DNS-323 but am wondering why yours is so much larger than the one Kylek put together. Yours is close to 3Mb while his is under 500k. There can't be that much difference between the "released" version and the nightly builds.

Also, after installing it, it still shows 7894 as the build.

Last edited by nohelp (2009-02-26 15:40:02)

KyleK wrote:

I just wanted to let you guys know that the overly high CPU usage of v1.50 has been fixed in the development builds. Transmission now uses around 20% CPU when downloading at 700kB/s, with rare spikes to 45%.
Also, mem usage seems to have been reduced as well.

The fix has been checked into the 1.5x branch, so I assume we'll see a 1.51 bugfix release shortly.

Nice to hear that. Waiting for a bugfix build.
BTW, it seems high CPU usage is happening only for torrents with 4MB pieces.

craft wrote:

Yes it still shows 7894 - dunno why - just downloaded the last svn. Maybe they forgett to change the version number...
I'm compiling with this options : --disable-gtk --disable-nls --disable-cli --perfix=/ffp
Maybe Kylek knows whats the difference (yeah, my one is 10 times bigger) between my version and his version.

regards

The version number is the old one because you forgot to delete libtransmission/version.h before compiling (it is automatically generated).

My releases contain the stripped binaries (since debugging Transmission on the NAS doesn't work anyway). That's why they're quite a bit smaller.

Upthread, Cirip was looking for a way to rename the file(s) downloaded by a torrent, but still continue to seed the torrent.  I suggested using links:

MCGlausa wrote:

Code:

# pause the torrent
# rename the file(s) or directory
$ mv /mnt/HD_a2/torrents/movie /mnt/HD_a2/torrents/music

# make the link to so Transmission can still seed the files
$ ln -s /mnt/HD_a2/torrents/music /mnt/HD_a2/torrents/movie

# resume the torrent

Now you essentially have two names for the directory '/mnt/HD_a2/torrents/music'.  Listing the directories with 'ls' should show the same files.

Later:

Cirip wrote:

It has a problem!

If I make it with this command there is a new directory called "music" but the "movie" directory still exist. And if I delete anything for example from the "music" it has been deleted to the "movie" too.
I would like to I have only the renamed directory.

As I said Cirip, my method works by having two names for the same file.  This is sort of like the idea of a shortcut in Windows, except you can open the link directly, instead of just using it to find the file to open.

As far as I know, there is no way to rename the file(s) and continue seeding the torrent.  My method allows you to keep seeding the torrent by having two names for the file(s) but only one copy on disk.  You're essentially saying "Transmission will call this file '/torrent/download/directory/fileX', everyone else can call it '/meaningful/path/name/fileY'".

I would suggest that instead of downloading directly to a "movie" or "music" directory, you download to a "downloads" directory.  Then when the torrent is seeding, you can use the pause-move-link method to organize the files the way you like.

Alternatively, you can just download each torrent to the directory you want by specifying the directory when you start downloading the torrent.  I believe the client you use (transmission-remote-gui) can do this, I also posted a way to do it using transmission-remote when you initially asked the question.

Hope this helps!

edit: fix stupid sign-off

Last edited by MCGlausa (2009-02-27 16:55:09)

Guys, I wouldn't bother with the "Move complete torrents" scripts. A patch is being developed for integration. I'd expect it for v1.60 or so.

Sorry, but no. I'm not on the developer team, I just follow it closely. Looking at their older releases I'd carefully estimate 4-6 weeks.

Should work again.

KyleK
i have some problem with 1.51:
i have 20+ seeding torrents and started downloading 2 torrents with 2 mbyte/s summary speed, after 1 (or less) hour web interface of transmission stop responding
but web interface(admin of dns-323), ftp, samba, ssh etc. on dns-323 works fine at that time, and transmission-daemon produces some activity (i see it with "top" command)
In 1.50 version this wasn't happened.

Last edited by Isildur (2009-02-28 01:04:09)

Yes, I noticed myself that Transmission scrapes stopped torrents. As far as I know there's no way to disable that in the current version.
As a workaround, you can either disable the logging altogether.

In order to do this, you have to edit transmission.sh. Change this line:

su $user -c "$command -f -g ${TRANSMISSION_HOME} 1>${TRANSMISSION_HOME}/$name.log 2>&1 &"

to this:

su $user -c "$command -f -g ${TRANSMISSION_HOME} 1>/dev/null 2>&1 &"

This will disable logging.
Alternatively, you can save the log to /tmp, which sits on the RAM portion of the NAS. The logs usually don't get very large, so you should be fine with that.

I'm still getting high CPU usage with 1.51, with just 3 torrents going. Is anyone else seeing this?