public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Limiting amount of memory a program can use.
Date: Mon, 29 Aug 2022 16:11:10 -0500	[thread overview]
Message-ID: <61d5e385-ad05-4201-4cc8-1c434f9da841@gmail.com> (raw)
In-Reply-To: <17d0992bbc7686d948669da3358388122ec4b414.camel@connell.tech>

Matt Connell wrote:
> How many torrents are you seeding, for a point of comparison?
>
> I use deluge (headless) on my home server, seeding anywhere from 500-
> 1000 individual torrents, representing ~5TB of total data, and the
> process is cruising along at just over 1GB of memory used.
>
> Maybe qbittorrent just doesn't scale well?  I feel like I'm on the
> exceedingly-high end of the spectrum with usage of a torrent program,
> but I don't know what everyone else is doing.
>
>


At one point, I had about 400 or so total, some downloading, some
finished and uploading while some were doing both.  I may have to switch
to something else before it is over.  I may even put it on a different
machine or use something else to put my videos on the TV, HTPC thingy.
Since I've found things that were hard to find elsewhere, I want to
return the favor.  So, I'd really like to hold onto those that are hard
to find. 

After I removed some of the inactive ones, it is a lot better.  I also
limited the upload speed which helped a lot.  According to atop, when
uploading at higher speeds, the reads were really putting a load on that
set of drives.  Does deluge have a GUI option?  Of course, if I put it
on another machine, I may go headless for it.  That's one reason I'm
asking.  Options.

And as soon as I think it is better, it slows down again and I find this
from top:


27672 dale      20   0  410.7g   4.3g   4.1g S   2.2  13.6 158:26.37
/usr/bin/qbittorrent


It's not nearly as bad as it was when I started this thread but still,
that's a lot of memory.

Dale

:-)  :-) 


  parent reply	other threads:[~2022-08-30  0:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28 12:24 [gentoo-user] Limiting amount of memory a program can use Dale
2022-08-28 12:56 ` Peter Humphrey
2022-08-28 13:03   ` Michael
2022-08-28 13:10     ` Michael
2022-08-28 14:21 ` Rich Freeman
2022-08-28 15:32   ` Wols Lists
2022-08-28 21:12     ` Rich Freeman
2022-08-28 14:24 ` Mark Knecht
2022-08-28 16:48 ` ralfconn
2022-08-29  5:50   ` Dale
2022-08-29 16:07 ` Matt Connell
2022-08-29 21:01   ` mad.scientist.at.large
2022-08-29 21:11   ` Dale [this message]
2022-08-30 13:56     ` Matt Connell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61d5e385-ad05-4201-4cc8-1c434f9da841@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox