WARNING A single process is both a transaction log and a storage server

[alexmiller]

@Vasilii

For best performance use dedicated disks for the transaction logs by setting process classes

Configuration — FoundationDB 7.1 is the official documentation on this subject, but there’s also been a number of threads over time. For example:

Cluster tuning cookbook

Hello everyone. I’m try to properly configure a cluster and struggling with the following behavior: There are 8 machines, each is 4 cores, 8GB of memory Each machine runs one FDB instance Engine is double ssd There are 5 coordinators in total Right now the transaction speed is just a little above 11k per second. Each transaction is 4 reads and 2 writes (non-atomics), key is around 64 bytes, value is less than 100 bytes. Looks like it’s quite underperforming and I’d appreciate some advice wh…

Production optimizations

Hi, Finally my cluster is up and running so I was able to do some significant testing. At this point, we’re using it as a cache, with a very simple transaction logic _, err = db.Transact(func(tr fdb.Transaction) (ret interface{}, err error) { future := tr.Get(sub.Pack(tuple.Tuple{"cache", ID})) res := future.MustGet() if len(res) == 0 { tr.Set(sub.Pack(tuple.Tuple{"cache", ID}), []byte(strconv.FormatInt(time.Now().UnixNano(), 10))) processChan <- id } ret…

Why doesn't my cluster performance scale when I double the number of machines?

Hello fellow FDB aficionado! I was wondering if you could help me identifying why I am not seeing any improvements after I scale my FDB cluster out. I have read the performance page and I know it is supposed to scale… I must be doing something incorrectly. Explanation: Let me be more specific with a benchmark I just run today using FDB 5.2 on linux on AWS/EC2. I started a cluster of 10 instances (i3.xlarge with NVME SSD 900GB high network throughput, 4vCPU). For information I ha…