5 ms·
A persistent key-value server in 40 lines and a sad fact (2014)
- callesgg 11y agoPS. The moving gif's make it very hard to read.
- kyberias 11y agoDon't look at the "moving gif's" (sic.). Then it will be easier to read.
- pluma 11y agoExcept 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).
- stefantalpalaru 11y agoWe'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.
- hawleyal 11y agoDisagree, chuckles
- 0942v8653 11y agoIf you're using Firefox, go into about:config and change image.animation_mode to none, then reload the page.
- juliangregorian 11y agoOr just use any browser's inspector to delete them.
- mpu 11y agoAgreed.
- javaispoo 11y agoMight 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.
- tlammens 11y agoStartup time in a server is a non-issue... Those processes keep running the whole time.
- javaispoo 11y agoYeah, 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.
- sarnowski 11y agoDon'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.
- vidarh 11y agoIn my real world the containers we spin up come up in seconds, but container restart is far more rare than restarting services.
- thescrewdriver 11y agoIf the time to restart your process or host affects the overall operation and performance of your service you're doing it wrong.
- astrange 11y agoThat 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.
- jpfr 11y agoThe 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).
- moru0011 11y agoits not "he" that's a JDK issue
- ninjaroar 11y agoChronicleMap looks really cool, i didn't know about it, but it seems like exactly what i've been looking for. I've been keeping an eye on apache directmemory, but that project seems to have little activity. does anyone here have real world experience with ChronicleMap in production systems?
- amelius 11y agoIf it is only 40 lines of code, why would you even use Java instead of e.g. C?
- moru0011 11y agoThen its 4000 lines ..
- digital-rubber 11y agoand the java engine is how many lines of code?
- ryanlol 11y agoWhich is still significantly less than with java.
- ExpiredLink 11y agoBut what is it? The author doesn't bother to describe problem definition and context.
- bradhe 11y agoCouple thoughts. 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.