linux-on-ibm-z/seastar

Name: seastar

Owner: LinuxONE and Linux on z Systems Open-source Team

Description: High performance server-side application framework

Created: 2017-01-26 12:34:00.0

Updated: 2017-01-26 12:34:03.0

Pushed: 2017-12-08 10:27:07.0

Homepage: http://seastar-project.org

Size: 5315

Language: C++

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

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, CentOS 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 too 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.