summaryrefslogtreecommitdiff
path: root/benchmarks/google_messages.proto
diff options
context:
space:
mode:
authorJoshua Haberman <jhaberman@gmail.com>2012-03-24 11:24:16 -0700
committerJoshua Haberman <jhaberman@gmail.com>2012-03-24 11:24:16 -0700
commit86bad61b76a260ffc442acffbe58feee67df45e5 (patch)
treee375e62ff6d7fea9fb810830e66118e67b4ec2c8 /benchmarks/google_messages.proto
parentdb59a5198f890ecdcac1227b0bb998160acac5c6 (diff)
Sync from internal Google development.
Many improvements, too many to mention. One significant perf regression warrants investigation: omitfp.parsetoproto2_googlemessage1.upb_jit: 343 -> 252 (-26.53) plain.parsetoproto2_googlemessage1.upb_jit: 334 -> 251 (-24.85) 25% regression for this benchmark is bad, but since I don't think there's any fundamental design issue that caused it I'm going to go ahead with the commit anyway. Can investigate and fix later. Other benchmarks were neutral or showed slight improvement.
Diffstat (limited to 'benchmarks/google_messages.proto')
-rw-r--r--benchmarks/google_messages.proto6
1 files changed, 6 insertions, 0 deletions
diff --git a/benchmarks/google_messages.proto b/benchmarks/google_messages.proto
index b43e94b..b367954 100644
--- a/benchmarks/google_messages.proto
+++ b/benchmarks/google_messages.proto
@@ -3,6 +3,11 @@ package benchmarks;
option optimize_for = SPEED;
+enum Foo {
+ FOO_VALUE = 1;
+ FOO_VALUE2 = 2;
+}
+
message SpeedMessage1 {
required string field1 = 1;
optional string field9 = 9;
@@ -45,6 +50,7 @@ message SpeedMessage1 {
optional int32 field128 = 128 [default=0];
optional string field129 = 129 [default="xxxxxxxxxxxxxxxxxxxxx"];
optional int32 field131 = 131 [default=0];
+ optional Foo field132 = 132 [default=FOO_VALUE];
}
message SpeedMessage1SubMessage {
generated by cgit on debian on lair
contact matthew@masot.net with questions or feedback