© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
int16receiver is the same benchmark as int16strings. It's not entirely clear why one datapoint got attributed to a differently named benchmark. Certainly we should fix that reporting, and prevent it from recurring.