public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: mad.scientist.at.large@tutanota.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Limiting amount of memory a program can use.
Date: Mon, 29 Aug 2022 23:01:23 +0200 (CEST)	[thread overview]
Message-ID: <NAfP9nG--3-2@tutanota.com> (raw)
In-Reply-To: <17d0992bbc7686d948669da3358388122ec4b414.camel@connell.tech>


--"Fascism begins the moment a ruling class, fearing the people may use their political democracy to gain economic democracy, begins to destroy political democracy in order to retain its power of exploitation and special privilege." Tommy Douglas




Aug 29, 2022, 10:07 by matt@connell.tech:

> 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.
>
Faster hard drives/striped raid array would help.  Also check out the "Advanced" section of the preferences in Qbit.  You can control memory use somewhat from there and definitely turn off multiple connections from the same host.


  reply	other threads:[~2022-08-29 21:01 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 [this message]
2022-08-29 21:11   ` Dale
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=NAfP9nG--3-2@tutanota.com \
    --to=mad.scientist.at.large@tutanota.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