-
Notifications
You must be signed in to change notification settings - Fork 38
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
Performance analysis / comparison #23
Comments
thanks a lot for your feedback, this is much appreciate it. speaking about your benchmark, I have a few questions to understand the full picture:
I'm sure I might have more question, but so looking forward to know more about this benchmark, this is a very good task. Thanks a lot, |
package main
import (
"log/syslog"
"log"
"time"
"sync/atomic"
)
func main() {
c, err := syslog.Dial("tcp", "172.16.91.128:12345", syslog.LOG_USER, "haha")
if err != nil {
log.Fatal(err)
}
count := int64(0)
go func() {
b := count
for {
n := count
log.Printf("rate: %d/s\n", n - b)
b = n
time.Sleep(time.Second)
}
}()
for {
c.Info("tick")
atomic.AddInt64(&count, 1)
}
} |
Thanks a lot for your clarification, i always find very necessary to provide clarification when writing numbers like this. Can you describe the VM you're using? SO? memory? CPU's? this matter for other trying to reproduce your numbers. Thanks |
VM has 4 CPUs (Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz) and 2gb of RAM. Logstash heap size is default. |
cool, thanks a lot. which OS are you using? |
Lt's a linux vm (boot2docker). |
awesome, I think now we've all necessary information. Thanks! |
Has there been any movement on this one? cc @untergeek |
Try 1,
syslog
input:With enabled output the following messages appear:
Performance is quite low:
Now try 2,
tcp
input +grok
filter:With enabled output the following messages appear:
Performance is much nicer, at least 12x:
Baseline
tcp
input without any processing:This is clearly suboptimal and there is a lot of room for improvement.
Logstash 2.0.0-beta3, oracle java 8u45.
The text was updated successfully, but these errors were encountered: