| import Stream._ | |
| /** A possibly finite stream that repeatedly applies a given function to a start value. | |
| * | |
| * @param start the start value of the stream | |
| * @param f the function that's repeatedly applied | |
| * @return the stream returning the possibly finite sequence of values `start, f(start), f(f(start)), ...` | |
| */ | |
| def iterate[A](f: A => A, a: A): Stream[A] = unfold((x: A) => Some((x, f(x))), a) |
| var data = "do shash'owania"; | |
| var crypto = require('crypto'); | |
| crypto.createHash('md5').update(data).digest("hex"); |
| package object mail { | |
| implicit def stringToSeq(single: String): Seq[String] = Seq(single) | |
| implicit def liftToOption[T](t: T): Option[T] = Some(t) | |
| sealed abstract class MailType | |
| case object Plain extends MailType | |
| case object Rich extends MailType | |
| case object MultiPart extends MailType |
| from math import cos, sin, atan2, sqrt | |
| def center_geolocation(geolocations): | |
| """ | |
| Provide a relatively accurate center lat, lon returned as a list pair, given | |
| a list of list pairs. | |
| ex: in: geolocations = ((lat1,lon1), (lat2,lon2),) | |
| out: (center_lat, center_lon) | |
| """ | |
| x = 0 |
| /** | |
| * Copyright (C) 2009-2014 Typesafe Inc. <http://www.typesafe.com> | |
| */ | |
| package akka.contrib.mailbox | |
| import scala.concurrent.duration._ | |
| import java.util.concurrent.atomic.AtomicInteger | |
| import java.util.concurrent.atomic.AtomicLong | |
| import com.typesafe.config.Config | |
| import akka.actor.{ ActorContext, ActorRef, ActorSystem, ExtendedActorSystem } |
Since many deployments may start out with 3 nodes and so little is known about how to grow a cluster from 3 memebrs to 5 members without losing the existing Quorum, here is an example of how this might be achieved.
In this example, all 5 nodes will be running on the same Vagrant host for the purpose of illustration, running on distinct configurations (ports and data directories) without the actual load of clients.
YMMV. Caveat usufructuarius.
Slightly disorganized but reasonably complete notes on the algorithms, strategies and optimizations of the Akka Cluster implementation. Could use a lot more links and context etc., but was just written for my own understanding. Might be expanded later.
Links to papers and talks that have inspired the implementation can be found on the 10 last pages of this presentation.
This is the Gossip state representation:
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
