Reed Allman c0df9496a7 reduce allocs in getSlotQueueKey (#778)
this somewhat minimally comes up in profiling, but it was an itch i needed to
scratch. this does 10x less allocations and is 3x faster (with 3x less bytes),
and they're the small painful kind of allocation. we're only reading these
strings so the uses of unsafe are fine (I think audit me).  the byte array
we're casting to a string at the end is also heap allocated and does
escape. I only count 2 allocations, but there's 3 (`hash.Sum` and
`make([]string)`), using a pool of sha1 hash.Hash shaves 120 byte and an alloc
off so seems worth it (it's minimal). if we set a max size of config vals with
a constant we could avoid that allocation and we could probably find a
checksum package that doesn't use the `hash.Hash` that would speed things up a
little (no dynamic dispatch, doesn't allocate in Sum) but there's not one I
know of in stdlib.

master:
```
✗: go test -run=yodawg -bench . -benchmem -benchtime 1s -cpuprofile cpu.out
goos: linux
goarch: amd64
pkg: github.com/fnproject/fn/api/agent
BenchmarkSlotKey          200000              6068 ns/op             696 B/op         31 allocs/op
PASS
ok      github.com/fnproject/fn/api/agent       1.454s
```

now:
```
✗: go test -run=yodawg -bench . -benchmem -benchtime 1s -cpuprofile cpu.out
goos: linux
goarch: amd64
pkg: github.com/fnproject/fn/api/agent
BenchmarkSlotKey         1000000              1901 ns/op             168 B/op          3 allocs/op
PASS
ok      github.com/fnproject/fn/api/agent       2.092s
```

once we have versioned apps/routes we don't need to build a sha or sort
configs so this will get a lot faster.

anyway, mostly funsies here... my life is that sad now.
2018-02-16 11:39:10 -08:00
2018-02-16 07:38:53 -08:00
2018-02-13 11:27:55 -08:00
2018-02-06 16:16:40 -08:00
2017-11-29 17:50:24 -08:00
2018-01-17 07:16:22 -08:00
2018-02-01 12:43:43 +00:00
2018-02-06 16:16:40 -08:00
2018-02-06 16:16:40 -08:00
2018-01-17 07:16:22 -08:00
2017-12-05 08:22:03 -08:00
2018-02-07 08:02:35 -08:00

Fn Project

Quickstart  |  Tutorials  |  Docs  |  API  |  Operating  |  Flow  |  UI

CircleCI GoDoc Go Report Card

Welcome

Fn is an event-driven, open source, Functions-as-a-Service (FaaS) compute platform that you can run anywhere. Some of its key features:

  • Open Source
  • Native Docker: use any Docker container as your Function
  • Supports all languages
  • Run anywhere
    • Public, private and hybrid cloud
    • Import Lambda functions and run them anywhere
  • Easy to use for developers
  • Easy to manage for operators
  • Written in Go
  • Simple yet powerful extensibility

The fastest way to experience Fn is to follow the quickstart below, or you can jump right to our full documentation, API Docs, or hit us up in our Slack Community!

Quickstart

Pre-requisites

  • Docker 17.06 or later installed and running
  • A Docker Hub account (Docker Hub) (or other Docker-compliant registry)
  • Log Docker into your Docker Hub account: docker login

Install CLI tool

The command line tool isn't required, but it sure makes things a lot easier. There are a few options to install it:

1. Homebrew - MacOS

If you're on a Mac and use Homebrew, this one is for you:

brew install fn

2. Shell script - Linux and MacOS

This one works on Linux and MacOS (partially on Windows):

curl -LSs https://raw.githubusercontent.com/fnproject/cli/master/install | sh

This will download a shell script and execute it. If the script asks for a password, that is because it invokes sudo.

3. Download the bin - Linux, MacOS and Windows

Head over to our releases and download it.

Run Fn Server

Now fire up an Fn server:

fn start

This will start Fn in single server mode, using an embedded database and message queue. You can find all the configuration options here. If you are on Windows, check here. If you are on a Linux system where the SELinux security policy is set to "Enforcing", such as Oracle Linux 7, check here.

Your First Function

Functions are small but powerful blocks of code that generally do one simple thing. Forget about monoliths when using functions, just focus on the task that you want the function to perform. Our CLI tool will help you get started super quickly.

Create hello world function:

fn init --runtime go hello

This will create a simple function in the directory hello, so let's cd into it:

cd hello

Feel free to check out the files it created or just keep going and look at it later.

# Set your Docker Hub username
export FN_REGISTRY=<DOCKERHUB_USERNAME>

# Run your function locally
fn run

# Deploy your functions to your local Fn server
fn deploy --app myapp --local

Now you can call your function:

curl http://localhost:8080/r/myapp/hello
# or:
fn call myapp /hello

Or in a browser: http://localhost:8080/r/myapp/hello

That's it! You just deployed your first function and called it. Try updating the function code in func.go then deploy it again to see the change.

Learn More

Get Help

Get Involved

Stay Informed

Description
The container native, cloud agnostic serverless platform.
Readme Apache-2.0 170 MiB
Languages
Go 97.4%
Shell 1.2%
Ruby 0.5%
Makefile 0.4%
Dockerfile 0.4%
Other 0.1%