Notices

7 pages of random bug fix information that i dont really understand, so sorry if this has been answered somewhere in there:
It says in the first post that youre going to check prolonged effect. any more on that?

How much does it use in terms of CPU and ram for just running in the background?

Very nice job btw

Um well aint nothin broke hear yet! That is the result of my prolonged 1 month test. Test still ongoing... will keep u informed!

Its probably less stressfull for flash memory than hard disks if thats any consolation... imagine hard disks saving to 20 different spots on the disk at once... lotta moving parts to wear out... u dont have that with flash. Flash will wear out but the actual files you download probably arent that bad since a 700mb file download (in transmission) acutally means each unit of memory is only written to once as soon as its received. It allocates and writes straight to the file... it doesnt move individual pieces around.

By default theres a small amount of data written (per download) to internal memory to manage the download. I requested a feature to allow (easy) relocation of this 'metadata' to fat based drives like sd/sdhc come by default... i havent heard anything back yet.

If you are super paranoid and want to limit internal flash usage see this (technical) post :
http://www.internettablettalk.com/fo...1&postcount=67

I have probably downloaded 10 or so gigs of data... on my 16 gig sd card thats less than one write per memory block... i think the individual blocks of flash memory are rated at about 100,000 writes or something... i think my isp would complain before my flash memory would

CPU utilization very high! Probably 60-100%! You can probably lower that by imposing peer limits or bandwith limits.

Dont know about memory load... i'll watch out for that next time.

yes, it's not trivial to work out how much file system I/O is caused when torrenting.

if you were downloading a 1G file by www or ftp, then each load of blocks would result in the file being extended, inodes updated/created each time. overall, there wouldn't be too many "hot spots" in the file system.

most torrent clients I've seen create a dummy file as big as the one being downloaded so that it can write each chunk as it comes, so that's probably BETTER than simply appending to a file as the filesys will create the chain of inodes etc on one go. however, depending on the design of the torrent client, the metadata might thrash the filesys unless it only uses RAM, but very large files will probably eat a lot of RAM for state information... my guess.

so, we're getting a bit technical, I'd like to know the answer, but maybe this is now the wrong forum!

Well i found where i can modify code to set cache directory, so i will try to build in a workaround for relocating cache data. I doubt this is necessary but will make us feel better knowing -nonreplacable- flash is not being thrashed.

If you have access to linux/macos desktop you could run install desktop version and run some kind of profiler on it.

If the first 'block' received is the last block of the file then the entire file will be allocated at once.... it allocates as it needs to... not sure how that affects inodes any differently.

looks great, but i am having some trouble with the torrent file. every time i try to open it, it says that the torrent file is not a valid... torrent file. i am not all that knowledgable when it comes to computers, so any and all help is appreciated.

Wel is it a valid torrent file? :P

thats the thing. i have no way of knowing if it is or not, and i know what i am about to say may not scream technically saavy, but is there a special directory/place/way that i have to save it? Or open it? (by the way it is saved as a .torrent file)

No special way/place. Just save and then open. I have had that happen maybe once and at the time i didnt really trust the source anyways so i just moved on. Is that the only torrent you've tried?

I guess you could attach the torrent file to a reply to this thread so we could look at it. Without knowing what your looking for i'd recommend trying some key tracker search engines like thepiratebay.org or xtvi.com which i've had alot of success with.

Unless its a legal torrent i dont think its a good idea to post it here

@ pipeline:

Thanks for this nice programm.

One thing is problematic: The first time I came across Transmission was before I read posts in this forum - I just browsed the Maemo Garage.

I tried downloading an image of Ubuntu 7.10 - but Transmission didn't react for ages and made the system act like it crashed... So I uninstalled it.

Now after reading all these posts I installed again and found out that it takes Transmission 4 to 5 minutes(!) to get started on this 700 MB file (downloading to removable SD card).

Maybe you should introduce some information that shows up the first time Transmission is started, informing users on the issues of CPU usage etc. Or maybe add s.th. to the summary text in the Maemo Garage.

Apart from that: Great app!

Cheers

Franko30