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

cpe210v1 rssi leds using 12%cpu #897

Closed
viisauksena opened this Issue Oct 3, 2016 · 10 comments

Comments

Projects
None yet
5 participants
@viisauksena
Contributor

viisauksena commented Oct 3, 2016

(rssileds is the feature which show rx level of ibss0 meshing network on the small leds on the side of cpe210 - as far as i know)

i suggest to let rssi leds only run for the first 15 minutes, or some other reasonable time ... so the 12% cpu and 2% Memory is free and available for fastd or other things

Mem: 28276K used, 32520K free, 252K shrd, 2216K buff, 7316K cached
CPU:  20% usr  26% sys   0% nic  16% idle   0% io   0% irq  36% sirq
Load average: 1.86 1.97 1.90 1/51 9861
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
 1644     1 root     R     3408   6%  49% /usr/bin/fastd --config - --daemon --
 1751     1 root     R     1216   2%  12% /usr/sbin/rssileds ibss0 40000 1 tp-l
 1606     1 root     R     1532   3%   5% /usr/sbin/hostapd -P /var/run/wifi-ph
@mweinelt

This comment has been minimized.

Show comment
Hide comment
@mweinelt

mweinelt Oct 3, 2016

Contributor

Or maybe just let the program update only in intervals, instead of hammering them so much that they flicker, at least thats what they feel like.

Contributor

mweinelt commented Oct 3, 2016

Or maybe just let the program update only in intervals, instead of hammering them so much that they flicker, at least thats what they feel like.

@rotanid rotanid added the enhancement label Oct 30, 2016

@TobleMiner

This comment has been minimized.

Show comment
Hide comment
@TobleMiner

TobleMiner Nov 2, 2016

Agreed. But this should be fixed in openwrt itself The default value is 40ms (25 refreshes per second) which is really fast. I think that 250 ms (4 refreshes per second) would be much more reasonable. I would suggest reopening this issue on the openwrt repo.

TobleMiner commented Nov 2, 2016

Agreed. But this should be fixed in openwrt itself The default value is 40ms (25 refreshes per second) which is really fast. I think that 250 ms (4 refreshes per second) would be much more reasonable. I would suggest reopening this issue on the openwrt repo.

@viisauksena

This comment has been minimized.

Show comment
Hide comment
@viisauksena

viisauksena Nov 2, 2016

Contributor

but this is also installed by default in gluon for cpe210 at least - so limiting rssileds in gluon in whatever-way also sounds reasonable

Contributor

viisauksena commented Nov 2, 2016

but this is also installed by default in gluon for cpe210 at least - so limiting rssileds in gluon in whatever-way also sounds reasonable

@TobleMiner

This comment has been minimized.

Show comment
Hide comment
@TobleMiner

TobleMiner Nov 2, 2016

Sure, gluon should fix this. But it is also "broken" in openwrt. Thus it should be fixed there, too.

TobleMiner commented Nov 2, 2016

Sure, gluon should fix this. But it is also "broken" in openwrt. Thus it should be fixed there, too.

@mweinelt

This comment has been minimized.

Show comment
Hide comment
@mweinelt

mweinelt Nov 2, 2016

Contributor

So can someone confirm 250ms to be a good value?

Decided for a 200ms interval by recommendation of @blocktrron.

Contributor

mweinelt commented Nov 2, 2016

So can someone confirm 250ms to be a good value?

Decided for a 200ms interval by recommendation of @blocktrron.

@viisauksena

This comment has been minimized.

Show comment
Hide comment
@viisauksena

viisauksena Nov 5, 2016

Contributor

so we wait until PR in openwrt is acknowledged and than build it in gluon (and whats than with upcoming LEDE) or we need own patch?

Contributor

viisauksena commented Nov 5, 2016

so we wait until PR in openwrt is acknowledged and than build it in gluon (and whats than with upcoming LEDE) or we need own patch?

@NeoRaider

This comment has been minimized.

Show comment
Hide comment
@NeoRaider

NeoRaider Nov 5, 2016

Member

We'll need a patch in Gluon as well.

@mweinelt, I think it would make sense to change the interval for all devices at once, not just for the CPE210/510.

Member

NeoRaider commented Nov 5, 2016

We'll need a patch in Gluon as well.

@mweinelt, I think it would make sense to change the interval for all devices at once, not just for the CPE210/510.

@mweinelt

This comment has been minimized.

Show comment
Hide comment
@mweinelt

mweinelt Nov 5, 2016

Contributor

So set 200ms for every device that has less than 200ms?

Contributor

mweinelt commented Nov 5, 2016

So set 200ms for every device that has less than 200ms?

@NeoRaider

This comment has been minimized.

Show comment
Hide comment
@NeoRaider

NeoRaider Nov 5, 2016

Member

Yes. A quick grep shows that all devices use the same interval of 40ms at the moment.

Member

NeoRaider commented Nov 5, 2016

Yes. A quick grep shows that all devices use the same interval of 40ms at the moment.

@viisauksena

This comment has been minimized.

Show comment
Hide comment
@viisauksena

viisauksena Nov 12, 2016

Contributor

is there a place where i can change it once , or do i have to change all the profiles with a patch?

Contributor

viisauksena commented Nov 12, 2016

is there a place where i can change it once , or do i have to change all the profiles with a patch?

@NeoRaider NeoRaider closed this in 9279fe4 Nov 16, 2016

NeoRaider added a commit that referenced this issue Nov 16, 2016

ecsv pushed a commit to FreifunkVogtland/gluon that referenced this issue Jun 9, 2017

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