Except that's now how human visual perception works. Movement is distracting and one of the main reason people hate banner ads (which historically have been extremely attention grabbing, occasionally resorting to strobing for maximum attention).
Our brains are geared for paying attention to things that move, especially things that move irregularly (like poorly looped gifs).
We're particularly attracted to movements outside the focus point, that's what makes it distracting. The retina cells (mainly rods) further away from the fovea are bad at distinguishing things, but excellent at detecting rapid movements.
It helps noticing prey when hunting or predators when being hunted. It does not help when trying to read some text.
1. 40 lines of glue code, sure. How much external code did he pull in/write?
2. All of this is predicated on the idea that serialization/deserialization is the primary bottleneck. This becomes not your bottleneck when you've got other distributed components in play.
The test highlights an issue not covered by micro-
benchmarking: Encoding and Decoding should perform
similar, as factual throughput is determined by
Min(Encoding performance, Decoding performance).
For unknown reasons JDK serialization manages to encode
the message tested like 500_000 times per second,
decoding performance is only 80_000 per second so in
the test the receiver gets dropped quickly:
At 500,000 messages/sec you can burn 6000 cycles per message on a 3Ghz core.
Probably he has a problem with malloc during the decoding phase.
Every malloc and every free costs between 300 (best case) and several thousand cycles (syscall is required).
Your JVM does. jruby.jar is megabytes of reimplementation and mapping of the Ruby stdlib onto the JVM. Plus in this example, loading a Ruby parser and interpreter.
Here's executing an assembly (über-jar) I wrote in Scala:
→ time scripts/couch
Please provide a basePath and a valid command. ("backup", "restore", "truncate", "migrate" or "migrate-all")
real 0m0.375s
user 0m0.415s
sys 0m0.073s
That's basically just `java -jar couch-utils.jar`.
A few hundred ms on my 1.2GHz MacBook. And this includes a bunch of Akka Actors.
Yeah, and memory is infinite, and all disks are free, and the computing fairies make all the processors super fast.
But back in the real world, startup time is a valid concern.
If your services consistently restart quickly, it gives you the freedom to design things differently.
E.g. doing a rolling update across a large number of instances by restarting a service at a time can become a quick enough process to be viable in instances where you'd otherwise need lots of excess capacity to be able to cycle larger proportions of instances at the same time. Making full rolling updates "cheaper" both in time and resources also translates to making rapid updates a safer choice (e.g. if I can roll back a broken release in 5 minutes, it's far safer to push out a new release than if a rollback takes hours).
That just means you expect restarting to be slow and have excluded it from your system design.
There is no problem with restarting nginx to update its config once a second, and it's even encouraged that you do so. Besides, crash-only software recovery is really the only morally sound development technique.
