Skip to content

CoolCamel/seastar

This branch is 6439 commits behind scylladb/seastar:master.

Folders and files

NameName
Last commit message
Last commit date
May 4, 2016
May 10, 2016
Mar 29, 2016
Mar 15, 2016
Sep 1, 2015
Mar 31, 2016
Jan 31, 2016
May 27, 2015
Sep 20, 2015
May 13, 2016
May 9, 2016
Apr 3, 2016
May 9, 2016
Mar 16, 2016
Nov 3, 2015
Oct 23, 2014
Jun 24, 2015
May 12, 2015
Jun 24, 2015
Feb 19, 2015
Jun 24, 2015
Jul 28, 2015
May 5, 2015
Feb 14, 2016
May 8, 2016
May 8, 2016

Repository files navigation

Seastar

Introduction

SeaStar is an event-driven framework allowing you to write non-blocking, asynchronous code in a relatively straightforward manner (once understood). It is based on futures.

Building Seastar

See instructions for Fedora and Ubuntu.

There are also instructions for building on any host that supports Docker.

Use of the DPDK is optional.

Getting started

There is a mini tutorial and a more comprehensive one.

The Native TCP/IP Stack

Seastar comes with its own userspace TCP/IP stack for better performance.

Recommended hardware configuration for SeaStar

  • CPUs - As much as you need. SeaStar is highly friendly for multi-core and NUMA
  • NICs - As fast as possible, we recommend 10G or 40G cards. It's possible to use 1G to but you may be limited by their capacity. In addition, the more hardware queue per cpu the better for SeaStar. Otherwise we have to emulate that in software.
  • Disks - Fast SSDs with high number of IOPS.
  • Client machines - Usually a single client machine can't load our servers. Both memaslap (memcached) and WRK (httpd) cannot over load their matching server counter parts. We recommend running the client on different machine than the servers and use several of them.

About

High performance server-side application framework

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • C++ 93.1%
  • Python 5.6%
  • Other 1.3%