Skip to content
This repository has been archived by the owner on Dec 31, 2022. It is now read-only.

Any way to limit CPU consumption and/or used bandwith? #155

Open
jpmath54 opened this issue Dec 6, 2021 · 3 comments
Open

Any way to limit CPU consumption and/or used bandwith? #155

jpmath54 opened this issue Dec 6, 2021 · 3 comments
Assignees
Labels
good first issue Good for newcomers

Comments

@jpmath54
Copy link

jpmath54 commented Dec 6, 2021

First of all, I would like to throw some congrats about the work done here, really a lifesaver.

Now my concern :
I'm farming XCH + 9 forks.
When I add Farmr, I see a real drop in my available (and also not really powerfull) DSL bandwithn and capacity to log remotely.

I'm thinking about monitoring only XCH and only one fork, but I really like the idea to have all of them at a glance on my smartphone...

Is there any mechanism to limit the BW consumption of farmr, maybe a way to reduce reports frequency or log analysis?
Sorry if it is already documented, Didn't found out in the github documentation.

@jpmath54 jpmath54 changed the title Any way to limit used bandwith? Any way to limit CPU consumption and/or used bandwith? Dec 6, 2021
@gilnobrega
Copy link
Owner

Yes, you can clone the repository, change this constant to the value you want in the source code

const Duration delay = Duration(minutes: 10); //10 minutes delay between updates

Then you can compile farmr by following these instructions https://github.com/gilnobrega/farmr/blob/main/docs/installation-source.md

Keep in mind that any value above 30 minutes will trigger the "Device is offline" notification. This is handled by the server and there is nothing you can do about it at the moment.

The server code is being rewritten to allow people to host their own servers and customise these values.

@gilnobrega gilnobrega added the good first issue Good for newcomers label Dec 13, 2021
@gilnobrega
Copy link
Owner

Performance issues with log parsing are being addressed in e77db97
It should perform much better in 1.7.8

@gilnobrega gilnobrega self-assigned this Jan 7, 2022
@gilnobrega gilnobrega pinned this issue Jan 7, 2022
@gilnobrega
Copy link
Owner

Addressed in v1.8.0.0
3a60401

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants