A demonstration of the autoscaling capabilities of an Elafros Revision.
Deploy the autoscale app to Elafros from the root directory.
bazel run sample/autoscale:everything.createExport your Ingress IP as SERVICE_IP.
# Put the Ingress Host name into an environment variable.
export SERVICE_HOST=`kubectl get route autoscale-route -o jsonpath="{.status.domain}"`
# Put the Ingress IP into an environment variable.
export SERVICE_IP=`kubectl get ingress autoscale-route-ela-ingress -o jsonpath="{.status.loadBalancer.ingress[*]['ip']}"`Request the largest prime less than 40,000,000 from the autoscale app. Note that it consumes about 1 cpu/sec.
time curl --header "Host:$SERVICE_HOST" http://${SERVICE_IP?}/primes/40000000Ramp up a bunch of traffic on the autoscale app (about 300 QPS).
kubectl delete namespace hey --ignore-not-found && kubectl create namespace hey
for i in `seq 2 2 60`; do
kubectl -n hey run hey-$i --image josephburnett/hey --restart Never -- \
-n 999999 -c $i -z 2m -host $SERVICE_HOST \
"http://${SERVICE_IP?}/primes/40000000"
sleep 1
done
watch kubectl get pods -n hey --show-allWatch the Elafros deployment pod count increase.
watch kubectl get deployLook at the latency, requests/sec and success rate of each pod.
for i in `seq 4 4 120`; do kubectl -n hey logs hey-$i ; done | lesskubectl delete namespace hey
bazel run sample/autoscale:everything.delete