A persistent key-value server in 40 lines and a sad fact (2014)
java-is-the-new-c.blogspot.com
A persistent key-value server in 40 lines and a sad fact (2014)
1–10 of 36 posts
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#2PS. The moving gif's make it very hard to read.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#3PS. The moving gif's make it very hard to read.
Don't look at the "moving gif's" (sic.). Then it will be easier to read.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#4Might be quick when running but the jvm startup time is a pain.
By the time the java solution starts up, my c based solution has already finished.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#5Might be quick when running but the jvm startup time is a pain. By the time the java solution starts up, my c based solution has already finished.
Startup time in a server is a non-issue... Those processes keep running the whole time.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#6Might be quick when running but the jvm startup time is a pain. By the time the java solution starts up, my c based solution has already finished.
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.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#7Might be quick when running but the jvm startup time is a pain. By the time the java solution starts up, my c based solution has already finished.
http://blog.ndk.io/2014/02/11/jvm-slow-startup.html
40ms sounds okay for me, even for most command line tools. Oh and I most probably don't get a segmentation fault ;-)
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#8Earlier 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.
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.
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#9PS. The moving gif's make it very hard to read.
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).
Re: A persistent key-value server in 40 lines and a sad fact (2014)
#10Might be quick when running but the jvm startup time is a pain. By the time the java solution starts up, my c based solution has already finished.
http://blog.ndk.io/2014/02/11/jvm-slow-startup.html 40ms sounds okay for me, even for most command line tools. Oh and I most probably don't get a segmentation fault ;-)
That rather proves the opposite: 6s Clojure startup time, for reasons that aren't obvious enough to be included in that blog post.