Milliseconds in your DateTimes or Timestamps.
We got 'em, you want 'em.
NOTE: only MySQL 5.6.4 and above supports DATETIME's with more precision than a second. For reference see MySQL 5.6.4 Changelog
Shit needs to be PRECISE
require 'benchmark' | |
require 'sidekiq-ent' | |
require 'redis-lock' | |
require 'redis-semaphore' | |
require 'ruby_redis_lock' | |
# monkey patch to remove exponential backoff in pmckee11-redis-lock, | |
# otherwise this benchmark does not complete successfully. | |
class Redis | |
class Lock |
option_settings: | |
- namespace: aws:elasticbeanstalk:cloudwatch:logs | |
option_name: StreamLogs | |
value: true | |
- namespace: aws:elasticbeanstalk:cloudwatch:logs | |
option_name: DeleteOnTerminate | |
value: false | |
- namespace: aws:elasticbeanstalk:cloudwatch:logs | |
option_name: RetentionInDays | |
value: 14 |
Milliseconds in your DateTimes or Timestamps.
We got 'em, you want 'em.
NOTE: only MySQL 5.6.4 and above supports DATETIME's with more precision than a second. For reference see MySQL 5.6.4 Changelog
Shit needs to be PRECISE
package main | |
import ( | |
"errors" | |
"github.com/streadway/amqp" | |
"log" | |
"os" | |
"time" | |
) |
There are 3 primary ways to pass data into functions: move, copy, or borrow (aka a reference). Since mutability is inherently intertwined with data passing (this function can borrow my data, but only if they promise not to mess with it), we end up with 6 distinct combinations.
Every language has its own level of support and take on these semantics:
Kafka 0.11.0.0 (Confluent 3.3.0) added support to manipulate offsets for a consumer group via cli kafka-consumer-groups
command.
kafka-consumer-groups --bootstrap-server <kafkahost:port> --group <group_id> --describe
Note the values under "CURRENT-OFFSET" and "LOG-END-OFFSET". "CURRENT-OFFSET" is the offset where this consumer group is currently at in each of the partitions.
L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns
Compress 1K bytes with Zippy ............. 3,000 ns = 3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns = 20 µs
SSD random read ........................ 150,000 ns = 150 µs
Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs