Marco Morais marcoemorais
| package services | |
| import ( | |
| "os" | |
| "time" | |
| log "github.com/Sirupsen/logrus" | |
| "github.com/garyburd/redigo/redis" | |
| ) |
| /* | |
| * Demo of libpq. | |
| * Build: g++ libpq-demo.cc -o libpq-demo -lpq | |
| * Run: ./libpq-demo | |
| */ | |
| #include <arpa/inet.h> | |
| #include <iostream> | |
| #include <libpq-fe.h> | |
| #include <sstream> |
Just documenting docs, articles, and discussion related to gRPC and load balancing.
https://github.com/grpc/grpc/blob/master/doc/load-balancing.md
Seems gRPC prefers thin client-side load balancing where a client gets a list of connected clients and a load balancing policy from a "load balancer" and then performs client-side load balancing based on the information. However, this could be useful for traditional load banaling approaches in clound deployments.
https://groups.google.com/forum/#!topic/grpc-io/8s7UHY_Q1po
gRPC "works" in AWS. That is, you can run gRPC services on EC2 nodes and have them connect to other nodes, and everything is fine. If you are using AWS for easy access to hardware then all is fine. What doesn't work is ELB (aka CLB), and ALBs. Neither of these support HTTP/2 (h2c) in a way that gRPC needs.
| """ | |
| author: Timothy C. Arlen | |
| date: 28 Feb 2018 | |
| Calculate Mean Average Precision (mAP) for a set of bounding boxes corresponding to specific | |
| image Ids. Usage: | |
| > python calculate_mean_ap.py | |
| Will display a plot of precision vs recall curves at 10 distinct IoU thresholds as well as output |
X1C6 Type: 20KG*
Bionic works out of the box on the new 2018 X1 Carbon. The X1C6 is a beautiful laptop, and Bionic is the best Ubuntu yet. Users of all levels of experties/experiences are recommended to try this combination. The purpose of this documentation is to improve the user's experience.
Following changes are required by the DSDT patch:
- Turn off Secure Boot