recentpopularlog in

kme : architecture   34

Hardware | Elasticsearch: The Definitive Guide [2.x] | Elastic
A machine with 64 GB of RAM is the ideal sweet spot, but 32 GB and 16 GB machines are also common. Less than 8 GB tends to be counterproductive (you end up needing many, many small machines), and greater than 64 GB has problems that we will discuss in Heap: Sizing and Swapping.


Interesting node about the I/O scheduler used on a system with SSDs:
Check Your I/O Scheduler

If you are using SSDs, make sure your OS I/O scheduler is configured correctly. When you write data to disk, the I/O scheduler decides when that data is actually sent to the disk. The default under most *nix distributions is a scheduler called cfq (Completely Fair Queuing).

This scheduler allocates time slices to each process, and then optimizes the delivery of these various queues to the disk. It is optimized for spinning media: the nature of rotating platters means it is more efficient to write data to disk based on physical layout.

This is inefficient for SSD, however, since there are no spinning platters involved. Instead, deadline or noop should be used instead. The deadline scheduler optimizes based on how long writes have been pending, while noop is just a simple FIFO queue.

This simple change can have dramatic impacts. We’ve seen a 500-fold improvement to write throughput just by using the correct scheduler.
searchandindex  sysadmin  elasticsearch  architecture  systemrequirements  performance 
10 weeks ago by kme
What the heck are you actually using NoSQL for? - High Scalability -
Has an impressive list of references at the bottom, for further reading.
API limiting. This is a great fit for Redis as a rate limiting check needs to be made for every single API hit, which involves both reading and writing short-lived data.
webdevel  devel  database  dba  architecture  nosql  explained  butwhy  forethereferences 
november 2019 by kme
Why the high-tech ideas of ‘Bucky’ Fuller are back in vogue | Aeon Essays
Fuller’s advocacy of technology as a salve for the wounds of modernity found a fierce critic in the sociologist Lewis Mumford, who longed for a more organic humanism. The two men proposed such contrasting versions of the future that Horizon magazine wondered, in 1968: ‘Which guide to the Promised Land? Fuller or Mumford?’ Mumford deplored the sterility of the sort of future that techno-faddists wanted for the human race. In an acid passage from 1956 that might have been aimed squarely at Fuller and his bubble-domed cities, Mumford wrote:

If the goal of human history is a uniform type of man, reproducing at a uniform rate, in a uniform environment, kept at a constant temperature, pressure and humidity, like a uniformly lifeless existence, with his uniform physical needs satisfied by uniform goods… most of the problems of human development would disappear. Only one problem would remain: why should anyone, even a computer, bother to keep this kind of creature alive?
humanity  thefuture  design  architecture 
january 2017 by kme

Copy this bookmark:





to read