Explorar el Código

benchmark: working-team: update version

conectado hace 4 años
padre
commit
5f9269285b

+ 1 - 2
Cargo.lock

@@ -2105,7 +2105,6 @@ dependencies = [
  "pallet-versioned-store",
  "pallet-versioned-store-permissions",
  "pallet-working-group",
- "pallet-working-team",
  "parity-scale-codec",
  "serde",
  "sp-api",
@@ -3893,7 +3892,7 @@ dependencies = [
 
 [[package]]
 name = "pallet-working-team"
-version = "1.0.0"
+version = "1.0.1"
 dependencies = [
  "frame-benchmarking",
  "frame-support",

+ 1 - 2
runtime-modules/working-team/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "pallet-working-team"
-version = "1.0.0"
+version = "1.0.1"
 authors = ['Joystream contributors']
 edition = '2018'
 
@@ -15,7 +15,6 @@ sp-std = { package = 'sp-std', default-features = false, git = 'https://github.c
 common = { package = 'pallet-common', default-features = false, path = '../common'}
 membership = { package = 'pallet-membership', default-features = false, path = '../membership'}
 balances = { package = 'pallet-balances', default-features = false, git = 'https://github.com/paritytech/substrate.git', rev = '00768a1f21a579c478fe5d4f51e1fa71f7db9fd4'}
-
 frame-benchmarking = { package = 'frame-benchmarking', default-features = false, git = 'https://github.com/paritytech/substrate.git', rev = '00768a1f21a579c478fe5d4f51e1fa71f7db9fd4', optional = true}
 
 [dev-dependencies]

+ 7 - 6
runtime-modules/working-team/src/benchmarking.rs

@@ -16,6 +16,7 @@ use crate::Module as WorkingTeam;
 use membership::Module as Membership;
 
 const SEED: u32 = 0;
+const MAX_BYTES: u32 = 16384;
 
 enum StakingRole {
     WithStakes,
@@ -512,7 +513,7 @@ benchmarks_instance! {
     }
 
     apply_on_opening {
-        let i in 1 .. 50000;
+        let i in 1 .. MAX_BYTES;
 
         let (lead_account_id, lead_member_id) = member_funded_account::<T>("lead", 0);
         let opening_id = add_opening_helper::<T, I>(
@@ -679,7 +680,7 @@ benchmarks_instance! {
     // Regular worker is the worst case scenario since the checks
     // require access to the storage whilist that's not the case with a lead opening
     slash_stake {
-        let i in 0 .. 50000;
+        let i in 0 .. MAX_BYTES;
 
         let (lead_id, lead_worker_id) =
             insert_a_worker::<T, I>(StakingRole::WithoutStakes, JobOpeningType::Leader, 0, None);
@@ -700,7 +701,7 @@ benchmarks_instance! {
     }
 
     terminate_role_worker {
-        let i in 0 .. 50000;
+        let i in 0 .. MAX_BYTES;
 
         let (lead_id, _) =
             insert_a_worker::<T, I>(StakingRole::WithoutStakes, JobOpeningType::Leader, 0, None);
@@ -724,7 +725,7 @@ benchmarks_instance! {
     }
 
     terminate_role_lead {
-        let i in 0 .. 50000;
+        let i in 0 .. MAX_BYTES;
 
         let (_, lead_worker_id) =
             insert_a_worker::<T, I>(StakingRole::WithStakes, JobOpeningType::Leader, 0, None);
@@ -832,7 +833,7 @@ benchmarks_instance! {
     }
 
     set_status_text {
-        let i in 0 .. 50000;
+        let i in 0 .. MAX_BYTES;
 
         let (lead_id, _) =
             insert_a_worker::<T, I>(StakingRole::WithoutStakes, JobOpeningType::Leader, 0, None);
@@ -883,7 +884,7 @@ benchmarks_instance! {
     // Regular opening is the worst case scenario since the checks
     // require access to the storage whilist that's not the case with a lead opening
     add_opening {
-        let i in 0 .. 50000;
+        let i in 0 .. MAX_BYTES;
 
         let (lead_id, _) =
             insert_a_worker::<T, I>(StakingRole::WithoutStakes, JobOpeningType::Leader, 0, None);