Admittedly, operation via Rancher comes with its own complexities: setting up security groups and IAM roles. These are documented of course, but as you say: minimum effort remains non-trivial.
323 karma · joined June 25, 2015
Admittedly, operation via Rancher comes with its own complexities: setting up security groups and IAM roles. These are documented of course, but as you say: minimum effort remains non-trivial.
Rancher 2 has a nicer UI and is more tightly related to Kubernetes. But there are moreorless zero docs, so be careful.
With either version: it's trivial to grab the master and node Docker images, and deploy them to your local machine to have a play.
Your bare metal hosts can be provisioned as Rancher hosts, which are dumb slaves managed by a Rancher server.
From the Rancher server, you can trivially express "I want this Docker container deployed across n Rancher hosts" or "I want 1 instance of this docker container across all Rancher hosts with the tag "has public IP".
You can group your Rancher hosts into Sandbox and Prod Rancher environments. You can easily install Rancher's load balancer service on them, or mount network storage, or register secrets upon them (like private Docker registry keys).
It also gives you health checks, host monitoring, and zero downtime redeploys. Super easy to use from the UI or CLI. Easy to install, too.
https://github.com/crystal-lang/crystal/issues/3067#issuecom...
IIRC it was due to a bug in glibc >= 2.1. Something about how mallocs are pooled. IIRC you need to tune it to be <= num of physical threads. Usually people advise 4 or 2.
# openjdk 8 bug: HotSpot leaking memory in long-running requests
# workaround:
# - Disable HotSpot completely with -Xint
# - slows the memory growth, but does not halt it:
MALLOC_ARENA_MAX=4
So, ensure that your java process is launched with that environment var (so, export it in the same shell, or precede your java command with it).If you happen to be using Tomcat, I recommend putting:
export MALLOC_ARENA_MAX=4
into: /usr/local/tomcat/bin/setenv.sh
As for how much memory you allocate to your containers: as of JRE 8u131 you can make this far more container-friendly: -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap
This is equivalent to saying: -XX:MaxRAM=$(cat /sys/fs/cgroup/memory/memory.limit_in_bytes)
https://github.com/moby/moby/issues/15020
https://github.com/docker-library/openjdk/issues/57
https://bugs.openjdk.java.net/browse/JDK-8170888I created speech bindings for my most common navigation tasks:
- "Down" -> presses PgDn
- "Down a bit" -> presses "down" a few times
- "Switch" -> presses Cmd+Tab (next application)
- "Backtick" -> presses Cmd+` (next window)
- "Apple L" -> presses Cmd+L (focus address bar)
Latency was good enough. Bindings have a higher priority than dictation, so if it hears one of your custom bindings: it will immediately action it instead of waiting to hear a full sentence.
Mac version was mostly only reliable for triggering keyboard shortcuts. Dictation of sentences worked pretty well, but there were (many) significant bugs that meant it was not generally viable.
I eventually stopped because of one of the following (can't recall):
- OS updates broke it - lost the license in a computer switch - hands got better