chore(su): clean su data storage code

servers/su/Cargo.toml

@@ -30,7 +30,6 @@ dashmap = "5.5.3"
 base64 = "0.21.5"
 actix-cors = "0.6.0"
 simd-json = "0.13.10"
-indicatif = "0.17.8"
 futures = "0.3.30"
 rocksdb = "0.22.0"
 

servers/su/README.md

@@ -40,6 +40,11 @@ Create a .env file with the following variables, or set them in the OS:
 - `UPLOAD_NODE_URL` an uploader url such as `https://up.arweave.net`
 - `MODE` can be either value `su` or `router` but for local development use `su`
 - `SCHEDULER_LIST_PATH` a list of schedulers only used for `router` MODE. Ignore when in `su` MODE, just set it to `""`.
+- `DB_WRITE_CONNECTIONS` how many db connections in the writer pool,defaults to 10
+- `DB_READ_CONNECTIONS` how many db connections in the reader pool, default to 10
+- `USE_DISK` whether or not to write and read rocksdb, this is a performance enhancement for the data storage layer
+- `SU_DATA_DIR` if `USE_DISK` is `true`, this is where rocksdb will be initialized
+- `MIGRATION_BATCH_SIZE` when running the migration binary how many to fetch at once from postgres
 
 > You can also use a `.env` file to set environment variables when running in
 > development mode, See the `.env.example` for an example `.env`
@@ -106,8 +111,12 @@ in the container.
 - `UPLOAD_NODE_URL` an uploader url such as `https://up.arweave.net`
 - `MODE` can be either value `su` or `router` but for local development use `su`
 - `SCHEDULER_LIST_PATH` a list of schedulers only used for `router` MODE. Ignore in `su` mode just set it to `""`.
-- `USE_DISK` whether or not to read and write message files from/to the disk/rocksdb. If the su has already been running for a while the data will need to be migrated using the mig binary before turning this on. This enhances the performance if the data is properly migrated to using the migration binary first.
-- `SU_DATA_DIR` The data directory on disk where the su will create a rocksdb key value store, it will only be used from if `USE_DISK` is `true`
+- `DB_WRITE_CONNECTIONS` how many db connections in the writer pool,defaults to 10
+- `DB_READ_CONNECTIONS` how many db connections in the reader pool, default to 10
+- `USE_DISK` whether or not to write and read rocksdb, this is a performance enhancement for the data storage layer
+- `SU_DATA_DIR` if `USE_DISK` is `true`, this is where rocksdb will be initialized
+- `MIGRATION_BATCH_SIZE` when running the migration binary how many to fetch at once from postgres
+
 
 
 ### Running a router in front of multiple scheduler units

servers/su/src/bin/mig.rs

@@ -1,4 +1,3 @@
-
 use std::io;
 
 use su::domain::migrate_to_disk;
@@ -7,4 +6,3 @@ use su::domain::migrate_to_disk;
 async fn main() -> io::Result<()> {
     migrate_to_disk().await
 }
-