[aw3c2]

It would be great to have a client that works well for seeding massive amounts of torrents (100,000+) on weak hardware (like a Raspberry). The main problem seems to be memory usage.

How is the memory usage of this one?

It says it is light-weight. What kind of light-weight is it and are there some metrics?

[Sir_Cmpwn]

Please help test it! We currently mean lightweight in terms of design, but we also want it to be lightweight in terms of performance. But we haven't had many opportunities to test it with truly huge numbers of torrents (though we have tested it on large torrents (1.5T+) with lots of files (1000+)).

As far as memory usage goes, I don't think low-memory devices have been a use-case Luminarys has had in mind yet, but he's probably on board with tuning with that in mind. On my client right now I have 45 torrents, 3 seeding, and one is that huge one I mentioned before - and synapse is using 1.2G of RAM, and 41G of virtual memory.

[UncleEntity]

That's a lot of memory...my little NAS has 512mb IIRC.

I run Transmission (from the Debian repo) on it and never even thought about memory usage before now, it just works. Admittedly I don't really let a bunch of torrents run at once though.

[ddevault]

Yeah. I've opened a ticket to audit memory usage:

https://github.com/Luminarys/synapse/issues/80

I should note that I'm stress testing it, however, I have some particularly large torrents going.

[shadeslayer]

Even if you solve the memory issues you will still be constrained by the NIC.

Most of these SBC's run ethernet over USB, so the performance is still going to be shit.

[andromeduck]

Probably still good enough to saturate the typical American broadband connection though.

[aw3c2]

If you want to just make sure that lots of content are accessible eventually that is neglible (and I am constrained by ISP anyways).

[thisacctforreal]

I recently selected an ODROID-C2 for a NAS because of its dedicated Ethernet controller. Cute device. My fingers are crossed for the performance test early this week.

[nly]

That's an interesting use case you have there... care to explain the motivation?

[aw3c2]

Wanting to make sure that lots of rare things stay accessible. ;)