Here's my experience of installing the NVIDIA CUDA kit 9.0 on a fresh install of Ubuntu Desktop 16.04.4 LTS.
Just documenting docs, articles, and discussion related to gRPC and load balancing.
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.
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.
A curated list of AWS resources to prepare for the AWS Certifications
A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.
In this article, I will share some of my experience on installing NVIDIA driver and CUDA on Linux OS. Here I mainly use Ubuntu as example. Comments for CentOS/Fedora are also provided as much as I can.
|# Outputs a pipeline that targets agents that have the same 'name' meta-data|
|# value as the step that does the pipeline upload. This means that all the|
|# steps will run on the same agent machine, assuming that the 'name' meta-data|
|# value is unique to each agent.|
|# Each agent needs to be configured with meta-data like so:|
|-- show running queries (pre 9.2)|
|SELECT procpid, age(clock_timestamp(), query_start), usename, current_query|
|WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%'|
|ORDER BY query_start desc;|
|-- show running queries (9.2)|
|SELECT pid, age(clock_timestamp(), query_start), usename, query|
|WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%'|