Packages

  • package root
    Definition Classes
    root
  • package com
    Definition Classes
    root
  • package twitter

    Start with com.twitter.finagle.

    Start with com.twitter.finagle.

    Definition Classes
    com
  • package finagle

    Finagle is an extensible RPC system.

    Finagle is an extensible RPC system.

    Services are represented by class com.twitter.finagle.Service. Clients make use of com.twitter.finagle.Service objects while servers implement them.

    Finagle contains a number of protocol implementations; each of these implement Client and/or com.twitter.finagle.Server. For example, Finagle's HTTP implementation, com.twitter.finagle.Http (in package finagle-http), exposes both.

    Thus a simple HTTP server is built like this:

    import com.twitter.finagle.{Http, Service}
import com.twitter.finagle.http.{Request, Response}
import com.twitter.util.{Await, Future}

val service = new Service[Request, Response] {
  def apply(req: Request): Future[Response] =
    Future.value(Response())
}
val server = Http.server.serve(":8080", service)
Await.ready(server)

    We first define a service to which requests are dispatched. In this case, the service returns immediately with a HTTP 200 OK response, and with no content.

    This service is then served via the Http protocol on TCP port 8080. Finally we wait for the server to stop serving.

    We can now query our web server:

    % curl -D - localhost:8080
HTTP/1.1 200 OK

    Building an HTTP client is also simple. (Note that type annotations are added for illustration.)

    import com.twitter.finagle.{Http, Service}
import com.twitter.finagle.http.{Request, Response}
import com.twitter.util.{Future, Return, Throw}

val client: Service[Request, Response] = Http.client.newService("localhost:8080")
val f: Future[Response] = client(Request()).respond {
  case Return(rep) =>
    printf("Got HTTP response %s\n", rep)
  case Throw(exc) =>
    printf("Got error %s\n", exc)
}

    Http.client.newService("localhost:8080") constructs a new com.twitter.finagle.Service instance connected to localhost TCP port 8080. We then issue a HTTP/1.1 GET request to URI "/". The service returns a com.twitter.util.Future representing the result of the operation. We listen to this future, printing an appropriate message when the response arrives.

    The Finagle homepage contains useful documentation and resources for using Finagle.

    Definition Classes
    twitter
  • package exp

    Package exp contains experimental code.

    Package exp contains experimental code. This can be removed or stabilized (moved elsewhere) at any time.

    Definition Classes
    finagle
  • package fiber_scheduler
    Definition Classes
    exp
  • package fiber
  • package util
  • FiberScheduler
  • FiberSchedulerOptimizer
  • FiberSchedulerService
  • package routing
    Definition Classes
    exp
p

com.twitter.finagle.exp

fiber_scheduler

package fiber_scheduler

Linear Supertypes
AnyRef, Any
Ordering
  1. Alphabetic
  2. By Inheritance
Inherited
  1. fiber_scheduler
  2. AnyRef
  3. Any
  1. Hide All
  2. Show All
Visibility
  1. Public
  2. Protected

Package Members

  1. package fiber
  2. package util

Type Members

  1. final class FiberScheduler extends ForkingScheduler

    ******************** *** EXPERIMENTAL *** ********************

    ******************** *** EXPERIMENTAL *** ********************

    The Fiber Scheduler uses fibers to implement a high-performance mechanism for the execution of Future computations via load balancing, work stealing, and continuation affinity.

    Fibers are created via the fork methods and they continue to be valid even after async boundaries. All Future continuations of a fiber are grouped by execution within the fiber itself. Nested fibers exchange continuations at their boundaries, providing a seamless mechanism to handle thread scheduling of Future computations.

    This Scheduler can be used in parallel to other thread pools but it is also carefully crafted to support all of an application's workload, including blocking and CPU-intensive operations. If enabled with the default configuration, FuturePool tasks are automatically redirected to the Fiber Scheduler.

    The adaptive size mechanism automatically adapts the number of worker threads to achieve peak throughput and avoid known Aurora limits like CPU throttling and container memory usage.

  2. final class FiberSchedulerService extends FinagleSchedulerService

    Service-loaded implementation used by FinagleScheduler to allow users to enable the Fiber Scheduler using the flag com.twitter.finagle.exp.scheduler.

Value Members

  1. object FiberScheduler
  2. object FiberSchedulerOptimizer

    Creates an Optimizer with the necessary configuration to support a FiberScheduler.

Inherited from AnyRef

Inherited from Any

Ungrouped