Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tor task higly increases CPU load #4045

Open
larrykind opened this issue Apr 16, 2024 · 4 comments
Open

Tor task higly increases CPU load #4045

larrykind opened this issue Apr 16, 2024 · 4 comments

Comments

@larrykind
Copy link

What version of GlobaLeaks are you using?

4.14.8 - os: debian 12

What browser(s) are you seeing the problem on?

No response

What operating system(s) are you seeing the problem on?

Linux

Describe the issue

When globaleaks performs this operation (Tor discovery / checking) my server CPU load goes to 100%. This process really stucks every front end interactions leaving the client with "loading" icon until the task ends (about 2 minutes in my case).
Attaching an htop of my server.

immagine

Proposed solution

No response

@evilaliv3
Copy link
Member

Thank you @larrykind .

  1. is the system multitenant and if yes how many tenants are you running?
  2. where do you read "Tor discovery / checking" ?

@larrykind
Copy link
Author

@evilaliv3

  1. yes the system is multitenant, there are about 150 tenant on it
  2. I really don't know which operation Tor is executing, it was just an hypotesis due to higher netowr traffic while the Tor application was this CPU consuming

@evilaliv3
Copy link
Member

I think there is nothing particularly that we could do.

I think this is a known performance issue of Tor that i would have considered resolved with onion services v3.

What we could do is eventually to reduce the number of onion services from N to 1 and use subdomains on the same onion service.

@asn-d6 @meejah are you aware of any configuration that could help optimize running Tor with a large number of onion services? thank you!

@asn-d6
Copy link

asn-d6 commented Apr 16, 2024

@rha

I think there is nothing particularly that we could do.

I think this is a known performance issue of Tor that i would have considered resolved with onion services v3.

What we could do is eventually to reduce the number of onion services from N to 1 and use subdomains on the same onion service.

@asn-d6 @meejah are you aware of any configuration that could help optimize running Tor with a large number of onion services? thank you!

@rhatto

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants