Bug #5363
openspanTodt performance
0%
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.
Updated by Derik Barseghian almost 13 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