-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
proto: Unmarshal takes more than 100 seconds at 22k QPS #888
Comments
$ go version $ go env |
My local pb version is obtained with go get, how do I get its version? |
Any kind of pb.Unmarshal will call this method? I also call pb.Unmarshal elsewhere, and it is blocked here too.Equally time consuming |
My server load is very low. Not the same unmarshal object |
It is difficult to diagnose this without knowing:
|
|
What are the methods on |
If that's the full method set, it seems that |
Yes, that's the full method set. no XXX_{Marshal,Unmarshal}. |
Did you have the performance bottleneck about this lib? |
Yes, please.
Nope. The |
It's pretty much impossible to provide QPS metrics because the cost of a "query" is dependent on the user's workload.
The |
Unfortunately not. Without a minimal reproduction, it is very difficult for us to diagnose this. |
Is this normal performance?
mass goroutine are blocked at table_unmarshal.go:117
unmarshalInfoLock.Lock().
I use pb like that:
I got :
The text was updated successfully, but these errors were encountered: