# Cpu usage + segfaults

**URL:** <https://discuss.elastic.co/t/cpu-usage-segfaults/41100>\
**Category:** Beats\
**Created:** [February 5, 2016, 9:17pm UTC](https://discuss.elastic.co/t/cpu-usage-segfaults/41100 "2016-02-05T21:17:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jayme](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jayme/32/6008_2.png) [@Jayme](https://discuss.elastic.co/u/Jayme)\
**Post date:** [February 5, 2016, 9:17pm UTC](https://discuss.elastic.co/t/cpu-usage-segfaults/41100/1 "2016-02-05T21:17:59Z")

</div>

Hi,  
I've been trying out packetbeat as a potential new relic replacement but I'm a bit afraid that CPU usage is a bit too high to use this in production.  
I've installed this on one of my webservers and it's the highest consuming process on there:  
[![](https://dl.dropboxusercontent.com/s/mm3qkecb9nvhn9b/Screenshot%202016-02-05%2022.11.24.png?dl=0) ](https://dl.dropboxusercontent.com/s/mm3qkecb9nvhn9b/Screenshot%202016-02-05%2022.11.24.png?dl=0)

It's also spawning panic errors like hell in /var/log/messages  
Feb 5 21:15:46 web745 /go/src/github.com/elastic/beats/packetbeat/protos/memcache/plugin\_tcp.go:335 (0x4de83d)  
Feb 5 21:15:46 web745 /go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:112 (0x51172d)  
Feb 5 21:15:46 web745 /go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:148 (0x511f3c)  
Feb 5 21:15:46 web745 /go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:183 (0x6f8047)  
Feb 5 21:15:46 web745 /go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:101 (0x6f7581)  
Feb 5 21:15:46 web745 /go/src/github.com/elastic/beats/packetbeat/sniffer/sniffer.go:356 (0x526299)  
Feb 5 21:15:46 web745 /go/src/github.com/elastic/beats/packetbeat/beat/packetbeat.go:232 (0x4676fb)  
Feb 5 21:15:46 web745 /usr/local/go/src/runtime/asm\_amd64.s:1721 (0x464561)  
Feb 5 21:15:46 web745 /usr/local/go/src/runtime/asm\_amd64.s:437 (0x4621ee)  
Feb 5 21:15:46 web745 /usr/local/go/src/runtime/panic.go:423 (0x4307c9)  
Feb 5 21:15:46 web745 /usr/local/go/src/runtime/panic.go:42 (0x42ee89)  
Feb 5 21:15:46 web745 /usr/local/go/src/runtime/sigpanic\_unix.go:24 (0x44589a)

[![](https://dl.dropboxusercontent.com/s/nyrf3neh3td6wy2/Screenshot%202016-02-05%2022.15.15.png?dl=0) ](https://dl.dropboxusercontent.com/s/nyrf3neh3td6wy2/Screenshot%202016-02-05%2022.15.15.png?dl=0)

Any things that I can change to lower cpu usage.. the other issue is probably something that needs to be fixed upstream

Thx  
Jayme

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 9:55pm UTC](https://discuss.elastic.co/t/cpu-usage-segfaults/41100/2 "2017-07-05T21:55:59Z")

</div>


