SQLite as a Result File Format in OMNeT++ OMNeT++ Community Summit 2016, Brno University of Technology (FIT-BUT), Sept 15-16. Rudolf Hornig OMNeT++ Result Files ● Scalar and Vector files ● Contents: Contents: ○ Run description ○ Scalar file: (module, scalar, value), histograms, result attributes ○ Vector file: vector data: (module, vectorname, vector data = (timestamp+value)*) ● Current format: ○ utVectorManager" 7 Using SQLite Result Files from OMNeT++ IDE SQLite Result Files can be used from the IDE just like the text based format. 8 Using SQLite Result Files Directly There are several

Improving Go Backend Developer Experience in Grab Chew Chee Ming Grab Engineering Manager, Developer Experience ???????????? Durian eater in Dali, Yunnan ? Runs & Love the outdoors ☕ Makes and Breaks flow of engineers, lag time leads to lower productivity ● 1 min increased build time could result in landing code 1 hour later ● Build times too long p50 ~15mins p90 ~38mins ● Start

Release 4.3.0 • Concurrency • prefork (multiprocessing), • Eventlet, gevent • solo (single threaded) • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django ORM • Apache Cassandra, Elasticsearch • Serialization Celery Documentation, Release 4.3.0 celery[redis] for using Redis as a message transport or as a result backend. celery[sqs] for using Amazon SQS as a message transport (experimental). celery[tblib] for Memcached as a result backend (using pylibmc) celery[pymemcache] for using Memcached as a result backend (pure-Python implementation). celery[cassandra] for using Apache Cassandra as a result backend with DataStax

prefork (multiprocessing), • Eventlet, gevent • thread (multithreaded) • solo (single threaded) • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django ORM • Apache Cassandra, Elasticsearch, Riak using the librabbitmq C library. celery[redis] for using Redis as a message transport or as a result backend. celery[sqs] for using Amazon SQS as a message transport (experimental). celery[tblib] for Memcached as a result backend (using pylibmc) celery[pymemcache] for using Memcached as a result backend (pure-Python implementation). celery[cassandra] for using Apache Cassandra as a result backend with DataStax

prefork (multiprocessing), • Eventlet, gevent • thread (multithreaded) • solo (single threaded) • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django ORM • Apache Cassandra, Elasticsearch, Riak using the librabbitmq C library. celery[redis] for using Redis as a message transport or as a result backend. celery[sqs] for using Amazon SQS as a message transport (experimental). celery[tblib] for Memcached as a result backend (using pylibmc) celery[pymemcache] for using Memcached as a result backend (pure-Python implementation). celery[cassandra] for using Apache Cassandra as a result backend with DataStax

prefork (multiprocessing), • Eventlet, gevent • thread (multithreaded) • solo (single threaded) • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django ORM • Apache Cassandra, Elasticsearch, Riak using the librabbitmq C library. celery[redis] for using Redis as a message transport or as a result backend. celery[sqs] for using Amazon SQS as a message transport (experimental). celery[tblib] for Memcached as a result backend (using pylibmc) celery[pymemcache] for using Memcached as a result backend (pure-Python implementation). celery[cassandra] for using Apache Cassandra as a result backend with DataStax

Release 4.1.0 • Concurrency • prefork (multiprocessing), • Eventlet, gevent • solo (single threaded) • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django ORM • Apache Cassandra, Elasticsearch • Serialization using the librabbitmq C library. celery[redis] for using Redis as a message transport or as a result backend. celery[sqs] for using Amazon SQS as a message transport (experimental). 10 Chapter 2. Contents Memcached as a result backend (using pylibmc) celery[pymemcache] for using Memcached as a result backend (pure-Python implementation). celery[cassandra] for using Apache Cassandra as a result backend with DataStax

Release 4.2.1 • Concurrency • prefork (multiprocessing), • Eventlet, gevent • solo (single threaded) • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django ORM • Apache Cassandra, Elasticsearch • Serialization Celery Documentation, Release 4.2.1 celery[redis] for using Redis as a message transport or as a result backend. celery[sqs] for using Amazon SQS as a message transport (experimental). celery[tblib] for Memcached as a result backend (using pylibmc) celery[pymemcache] for using Memcached as a result backend (pure-Python implementation). celery[cassandra] for using Apache Cassandra as a result backend with DataStax

Release 4.2.2 • Concurrency • prefork (multiprocessing), • Eventlet, gevent • solo (single threaded) • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django ORM • Apache Cassandra, Elasticsearch • Serialization Celery Documentation, Release 4.2.2 celery[redis] for using Redis as a message transport or as a result backend. celery[sqs] for using Amazon SQS as a message transport (experimental). celery[tblib] for Memcached as a result backend (using pylibmc) celery[pymemcache] for using Memcached as a result backend (pure-Python implementation). celery[cassandra] for using Apache Cassandra as a result backend with DataStax

Release 4.2.0 • Concurrency • prefork (multiprocessing), • Eventlet, gevent • solo (single threaded) • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django ORM • Apache Cassandra, Elasticsearch • Serialization Celery Documentation, Release 4.2.0 celery[redis] for using Redis as a message transport or as a result backend. celery[sqs] for using Amazon SQS as a message transport (experimental). celery[tblib] for Memcached as a result backend (using pylibmc) celery[pymemcache] for using Memcached as a result backend (pure-Python implementation). celery[cassandra] for using Apache Cassandra as a result backend with DataStax