Brandon Kite

Re-genesis upgrade integration testing(advanced)

1

## Description Add tests that an existing chain can be snapshotted via the `fuel-core` CLI and restored onto a fresh node without breaking backward compatibility. It can be one test...

Post-deploy load testing

1

Setup a load test suite that runs at least nightly on the master CD environment.

Now that the RocksDB crate supports built-in transactions, evaluate whether it would be possible and more efficient to use those in place of the in-memory data store. https://docs.rs/rocksdb/0.20.1/rocksdb/struct.DBCommon.html#method.transaction

use pprof-rs and pyroscope in deployments to obtain realtime profiling info about fuel-core

There's a lot of complexity involved with adding new cli args to our deployment configurations. By allowing fuel-core to load these from a file, we wouldn't need to update our...

Integrate the GraphQL Client Backend with the GraphQL server for FuelCore. This should result in all the integration tests passing when using the GraphQL Client & Server. Blocked by: -...

Maybe we can calculate it one time at the begin of the `execute_create_or_script` method and pass it everywhere? _Originally posted by @xgreenx in https://github.com/FuelLabs/fuel-core/pull/1107#discussion_r1160938395_

Parallel transaction execution within blocks

3

One of the key benefits of fuel's transaction format and architecture is the capability to parallelize transactions execution. This issue is intended to cover the initial design and considerations for...

investigate gradual memory increase

1

In prod there is a gradual increase in memory usage for our nodes. We need to find out if this is a memory leak or just rocksdb caching. 

Add contract state API

1

Allow the sdk to fetch state from contracts to inspect the blockchain. This should probably also support range based lookups (similar to what the VM does).