Estimate the memory size of EIP-7702 transactions

[fab-10]

PR description

Estimate the memory size of EIP-7702 transactions and implement the detached copy of code delegation objects to avoid keeping references to big bytes arrays while the tx sits in the txpool

Fixed Issue(s)

fixes #7976

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests

[ahamlat]

Small comments, but nothing really blocking.

[ahamlat]

I see that the method is not used, why do we need to have it ? with no comment, it looks like a dead code for me.

[fab-10]

documented how to use this utility

[ahamlat]

Thanks for the detailed documentation, to access JMX mbeans, you need to have a java process running that exposes those Mbeans. I still don't see how can this work in a unit test. Could you give an example how can this work ?

[fab-10]

Just put it wherever you need, no other setup needed

  @Test
  public void baseFrontierAndAccessListTransactionMemorySize() {
    final Transaction txFrontier =
        createTransaction(TransactionType.FRONTIER, 1, Wei.of(500), 0, KEYS1);
    try {
      dumpHeap("/tmp/heap.hprof", true);
    } catch (IOException e) {
      throw new RuntimeException(e);
    }
    assertThat(baseTransactionMemorySize(txFrontier, FRONTIER_ACCESS_LIST_CONSTANT_FIELD_PATHS))
        .isEqualTo(FRONTIER_AND_ACCESS_LIST_SHALLOW_SIZE);
  }

[ahamlat]

Interesting, I generated two heap dumps, one with live=true and one with lives=false. I think it makes sens to do the test with live=false, as it keeps even objects that will be garbage collected. I could find for the example above the transaction only when live=false