Zokyo Gas Savings
  • โ›ฝZokyo Gas Savings
  • ๐Ÿ“šTutorials
    • โœ”๏ธGas Saving Technique 1: Unchecked Arithmetic
    • โ›“๏ธGas Saving Technique 2: Immutable Variable
    • โœจGas Saving Technique 3: Double star ** inefficiency
    • ๐Ÿ’ฐGas Saving Technique 4: Cache Array Length
    • โฌ…๏ธGas Saving Technique 5: ++i costs less gas compared to i++
    • โš–๏ธGas Saving Technique 6: NOT operator ! cheaper than boolean FALSE
    • ๐ŸชกGas Saving Technique 7: Using Short Reason Strings
    • ๐ŸชตGas Saving Technique 8: Use Custom Errors instead of Revert Strings to save Gas
    • โœ’๏ธGas Saving Technique 9: Use Custom Errors instead of Revert Strings to save Gas
    • ๐Ÿ‘พGas Saving Technique 10: Calldata cheaper than memory
    • โ›”Gas Saving Technique 11: > 0 is less efficient than != 0 for unsigned integers
    • โž—Gas Saving Technique 12: SafeMath no longer needed
    • ๐Ÿ˜ฎGas Saving Technique 13: variables default to 0
    • ๐ŸงฑGas Saving Technique 14: struct layout/ variable packing
    • ๐Ÿ“žGas Saving Technique 15: Cache External Call
    • โœ๏ธGas Saving Technique 16: Early Validation before external call
    • ๐Ÿ˜ŽGas Saving Technique 17: Donโ€™t cache value that is used once
    • ๐Ÿ˜งGas Saving Technique 18: Redundant code
    • โœ…Gas Saving Technique 19: Early Validation before external call
    • โ›๏ธGas Saving Technique 20: Storage vs Memory read optimizations
    • โœ’๏ธGas Saving Technique 21: Unneeded If statements
    • ๐ŸŒ—Gas Saving Technique 22: >= is cheaper than >
    • ๐ŸŽ’Gas Saving Technique 23: Public to private constants
    • โน๏ธGas Saving Technique 24: Make unchanged variables constant/immutable
    • โฑ๏ธGas Saving Techniques 25: Redundant Access Control Checks
    • โžก๏ธGas Saving Technique 26: Shift Right instead of Dividing by 2
    • ๐ŸชƒGas Saving Tutorial 27: Efficient Boolean Comparison
    • ๐ŸคGas Saving Technique 28: && operator uses more gas
    • ๐Ÿ‘“Gas Saving Technique 29: x = x + y is cheaper than x += y
    • ๐Ÿ‘‚Gas Saving Technique 30: Using 1 and 2 rather than 0 and 1 saves gas
    • โšฝGas Saving Technique 31: Optimize Storage by Avoiding Booleans
    • ๐Ÿ”™Gas Saving Technique 32: Optimal Use of Named Return Variables in Solidity
    • ๐Ÿ›ข๏ธGas Saving Technique 33: Making Functions Payable for Optimized Gas Costs
    • โœ๏ธGas Saving Technique 34: Optimizing Storage References in Smart Contracts
    • โ›ฐ๏ธGas Saving Technique 35: Usage of uints/ints smaller than 32 bytes (256 bits) incurs overhead
    • ๐ŸŒช๏ธGas Saving Technique 36: Inlining Single Use Internal Functions for Savings
    • โ˜„๏ธGas Saving Technique 37: Switching from Public to External Functions for Savings
    • ๐ŸŽ†Gas Saving Technique 38: Upgrading Solidity Compiler to Improve Gas Efficiency and Security
    • ๐Ÿ•ถ๏ธGas Saving Technique 39: Avoiding Duplicated Code for Gas Savings
    • ๐Ÿ˜„Gas Saving Technique 40: Removal of Unused Internal Functions for Gas Savings
    • ๐Ÿ–‹๏ธGas Saving Tutorial 41: In-lining Single Use Modifiers For Gas Saving
    • โ›๏ธGas Saving Technique 42: `require` vs`assert`
Powered by GitBook
On this page
  1. Tutorials

Gas Saving Technique 20: Storage vs Memory read optimizations

PreviousGas Saving Technique 19: Early Validation before external callNextGas Saving Technique 21: Unneeded If statements

Last updated 1 year ago

Introduction

In the realm of smart contracts, efficient gas usage is of the essence. An impactful method for economizing gas consumption is minimizing unnecessary storage reads, as reading from storage (using SLOAD) is considerably costly in terms of gas. This tutorial aims to shed light on how to optimize storage reads to save gas.

Impact & Details

Why Optimize Storage Reads?

  • Cost Efficiency: SLOAD operations are expensive, costing around 100 gas per operation, while MLOAD and MSTORE operations are considerably cheaper at approximately 3 gas each. Therefore, reducing SLOAD operations can lead to significant gas savings.

  • Optimized Performance: By caching storage variables in memory, you can enhance the contract's performance, making it more efficient and responsive.

Example: Storage Read Optimization

Before Optimization:

solidityCopy codepragma solidity ^0.8.0;

contract StorageOptimization {
    uint256[] public numbers;

    function calculateSum() public view returns (uint256) {
        uint256 sum = 0;
        for (uint256 i = 0; i < numbers.length; i++) {
            sum += numbers[i];  // Multiple SLOAD operations due to repeated storage reads
        }
        return sum;
    }
}

After Optimization:

solidityCopy codepragma solidity ^0.8.0;

contract StorageOptimization {
    uint256[] public numbers;

    function calculateSum() public view returns (uint256) {
        uint256 sum = 0;
        uint256 length = numbers.length;  // Caching the length in memory
        for (uint256 i = 0; i < length; i++) {
            sum += numbers[i];  // Reduces the number of SLOAD operations
        }
        return sum;
    }
}

Recommended Mitigation Steps

  1. Identify Repeated Storage Reads: Look for any storage variables being read multiple times within a function, especially within loops.

  2. Cache in Memory: Cache storage variables in memory if they are being read multiple times within the same function or scope, particularly in loops.

  3. Test for Gas Savings: After making adjustments, test the function to verify that it is not only still working as expected but also using less gas.

Conclusion

Minimizing storage reads by caching storage variables in memory significantly aids in reducing gas consumption, leading to more efficient and cost-effective smart contracts. Adopt this practice consistently across your smart contracts to ensure you're developing gas-optimized, high-performance decentralized applications. Always remember to test your contracts thoroughly after implementing these optimizations to ensure they work as intended.

๐Ÿ“š
โ›๏ธ
Book an audit with Zokyo