PS. The moving gif's make it very hard to read.
Agreed.
A persistent key-value server in 40 lines and a sad fact (2014)
21–30 of 36 posts
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#22Earlier quoted context omitted.
Don't look at the "moving gif's" (sic.). Then it will be easier to read.
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.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#23PS. The moving gif's make it very hard to read.
Disagree, chuckles
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#24But what is it? The author doesn't bother to describe problem definition and context.
Database/persistence server using serialization and key-value store.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#25Earlier quoted context omitted.
Don't know your "real" world. In my real world, the AWS instance takes several minutes to come up - I can spare some milliseconds on thr JVM startup.
In my real world the containers we spin up come up in seconds, but container restart is far more rare than restarting services.
If the time to restart your process or host affects the overall operation and performance of your service you're doing it wrong.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#26Earlier quoted context omitted.
Startup time in a server is a non-issue... Those processes keep running the whole time.
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.
What are you doing that you frequently starts / shuts down an application to the order where 70ms is a problem?
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#27But what is it? The author doesn't bother to describe problem definition and context.
He referenced Peter Lawrey, and the off-heap stuff he does with HFT systems, so presumably it's somewhere along those lines.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#28Earlier quoted context omitted.
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.
What are you doing that you frequently starts / shuts down an application to the order where 70ms is a problem?
Not just frequently starting/stopping applications but a persistence engine at that.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#29Earlier quoted context omitted.
Startup time in a server is a non-issue... Those processes keep running the whole time.
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.
How many reboots per second are you having to endure? Maybe you should make your server process crash less often.