Andrew Fitzgerald

#### Problem Implementation of #26923 for #27027 #### Summary of Changes Fixes #

#### Problem #27027 #### Summary of Changes More up to date verson of #26362 which fixes several bottlenecks with that proposal Fixes #

benchmarking code for transaction scheduler

3

#### Problem #### Summary of Changes A transaction-scheduler benchmarking tool, so we can have common testing for different scheduler implementations A big thanks to @buffalu, as I took a lot...

Updated fee transaction priority proposal

4

#### Problem Out of date and fee priority scheduler proposal #### Summary of Changes Updated the fee priority proposal for current idea of how we should schedule transacitons Fixes #

Replace the simple priority queueing scheduling with an algorithm that considers priority, time, and account read/write locks in the transaction. Blocked by #27010

A preliminary toward getting a more advanced scheduler: getting the current scheduling logic into its' own stage. This will likely be broken up into two parts: 1. Add a centralized...

Move packet deserialization into its' own stage

1

A separate transaction scheduling stage will rely on having the set of accounts used in each transaction. To achieve this we need to separate packet deserialization from the banking stage.

Add a measure_block macro

2

#### Problem The existing measure! macro can change the way we write our code, and is not always easy to use when we want access to several variables assigned in...

#### Problem I wanted an exampe for #26975 #### Summary of Changes Used measure! and measure_block! macros in banking_stage.rs as an example Fixes #

Feature: Interleaved Snapshot Untar and Indexing - Stage 1

1

#### Problem Much of the work in rebuilding accounts_db from snapshot(s) can be done while we are untaring the snapshot. #### Summary of Changes Separating the "interleaved untar & indexing"...