Opened 7 years ago

Closed 4 years ago

#784 closed defect (no response)

Total uploader limit not being utilized

Reported by: dg Owned by: zzz
Priority: minor Milestone:
Component: apps/i2psnark Version: 0.9.3
Keywords: Cc:
Parent Tickets:

Description

It would seem that the "total uploader limit" is not being utilized. I have had more than the current limit being used in my torrent(s), actively being connected to.

I'm not sure if the "total uploader limit" refers to peers which are actually being feeded pieces at any given time or those of which you are connected to, asking for those pieces. I'd rather it be the latter.

Subtickets

Change History (5)

comment:1 Changed 7 years ago by zzz

Detailed test results please. What did you set the limit to, how long did you wait after setting, and how many uploaders did you observe?

comment:2 Changed 7 years ago by dg

I set the limit to 4, and at least 30-60 minutes later, it was around 6+. Not a big deal, I understand, but the instance I was running snark on was very tiny and I was trying to regulate things.

comment:3 Changed 6 years ago by str4d

  • Milestone 0.9.4 deleted

comment:4 Changed 4 years ago by zzz

  • Status changed from new to infoneeded_new

It's the former, i.e. those actually being sent pieces.

There's a max connections per-torrent that defaults to 16 with an undocumented setting in the config file i2psnark.maxConnections=nnn.

There's no total max connections implemented.

Do you really think it sould be changed?

comment:5 Changed 4 years ago by zzz

  • Resolution set to no response
  • Status changed from infoneeded_new to closed

please reopen if you respond.

Note: See TracTickets for help on using tickets.