Opened 2 years ago

Closed 9 months ago

#24064 closed task (implemented)

Memory profiling of Tor on Android device

Reported by: ahf Owned by: ahf
Priority: Medium Milestone: Tor: 0.4.0.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: internal, 035-roadmap-subtask, 035-triaged-in-20180711
Cc: Actual Points:
Parent ID: #26630 Points:
Reviewer: Sponsor:

Description

We should collect measurements of memory usage on Android devices in a reproducible manner.

Child Tickets

Change History (20)

comment:1 Changed 2 years ago by ahf

Owner: set to ahf
Status: newassigned

comment:2 Changed 2 years ago by cypherpunks

And how can I optout from this "statistics collection"?

You do have an option for optout all-data-collecting right?

Be honest. Write this to download page or you'll become another evil google.
"If you use Tor, we collect your computer information and what onion you visit."
"Write xxxxx to torrc file to opt-out." <--- Ideas?

comment:4 Changed 2 years ago by nickm

cypherpunks, you seriously misunderstood the purposes of this ticket.

It is about doing our own measurements on our own devices under lab conditions, so we can find out how much memory Tor is using.

comment:5 Changed 2 years ago by ahf

Hello!

You don't have to opt in or out of anything.

This is an experiment we are doing on *my* (as in, the device I carry with me in my pocket) Android phone to figure out if we can make Tor use less memory - once we have some results from this, which you can look at for yourself, we will figure out some places in the Tor source code where we will optimise and see if we can make Tor perform better such that it uses less memory on Android phones. This will hopefully allow more people, even with inexpensive devices, to have a decent experience using Tor :-)

Last edited 2 years ago by ahf (previous) (diff)

comment:6 Changed 2 years ago by cypherpunks

Keywords: internal added

comment:7 Changed 2 years ago by cypherpunks

lol this cypherpunks misunderstood this ticket. But Tor project should tag properly.

I suggest "internal" tag or "teamonly" tag.

comment:8 Changed 19 months ago by dgoulet

Milestone: Tor: 0.3.4.x-final

comment:9 Changed 19 months ago by nickm

Keywords: 034-triage-20180328 added

comment:10 Changed 19 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:11 Changed 18 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

comment:12 Changed 16 months ago by nickm

Keywords: 035-roadmap-master added; 034-triage-20180328 034-removed-20180328 removed

comment:13 Changed 16 months ago by nickm

Parent ID: #24061#26630

comment:14 Changed 16 months ago by nickm

Milestone: Tor: unspecifiedTor: 0.3.5.x-final

comment:15 Changed 16 months ago by nickm

Keywords: 035-roadmap-subtask added; 035-roadmap-master removed

comment:16 Changed 15 months ago by nickm

Keywords: 035-triaged-in-20180711 added

comment:17 Changed 13 months ago by ahf

Milestone: Tor: 0.3.5.x-finalTor: 0.3.6.x-final

comment:18 Changed 11 months ago by nickm

Milestone: Tor: 0.3.6.x-finalTor: 0.4.0.x-final

Tor 0.3.6.x has been renamed to 0.4.0.x.

comment:19 Changed 9 months ago by gaba

Keywords: s8-perf s8-201710 removed
Sponsor: Sponsor8

comment:20 Changed 9 months ago by nickm

Resolution: implemented
Status: assignedclosed

We got the information we needed here as part of #28020.

Note: See TracTickets for help on using tickets.