Project

General

Profile

Bug #5363

spanTodt performance

Added by Derik Barseghian over 8 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Category:
sensor-view
Target version:
Start date:
04/01/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5363

Description

The spanTodt process is often hovering around 90% cpu usage on my gumstix (i'm currently sampling batt_volt every 5s, 2 other sensors every 30s, and we're still doing periodic (every 60s) metadata writes for each channel). I made logging pretty verbose, which probably isn't helping performance.
Would be good to improve this.

History

#1 Updated by Derik Barseghian over 8 years ago

It looks like spanTodt can also use up the gumstix memory to the point of the oom-killer being repeatedly invoked, including killing span-dcd:
---
Out of memory: kill process 1265 (dcd_mgr) score 206 or a child
Killed process 1265 (dcd_mgr)
java invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0
---

Before killing spanTodt:
---
MemTotal: 241596 kB
MemFree: 4788 kB
Buffers: 264 kB
Cached: 5648 kB
SwapCached: 0 kB
Active: 108124 kB
Inactive: 119648 kB
Active(anon): 107016 kB
Inactive(anon): 115024 kB
Active(file): 1108 kB
Inactive(file): 4624 kB
---

After killing spanTodt:
---
MemTotal: 241596 kB
MemFree: 195624 kB
Buffers: 288 kB
Cached: 4876 kB
SwapCached: 0 kB
Active: 5640 kB
Inactive: 31828 kB
Active(anon): 4528 kB
Inactive(anon): 27952 kB
Active(file): 1112 kB
Inactive(file): 3876 kB

#2 Updated by Derik Barseghian about 7 years ago

Moving to 1.x.y target.

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5363

Also available in: Atom PDF