Skip to content

Conversation

@dmkozh
Copy link
Contributor

@dmkozh dmkozh commented Jan 13, 2026

No description provided.

@leighmcculloch leighmcculloch merged commit b81b76b into stellar:master Jan 13, 2026
5 checks passed
## Preamble

```
SLP: 0003
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: 0004

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching that. We should get copilot to review prs for things like this. 🤔

| Write Entries | 50 | 200 | 500 | 1000 | 5 |
| Write Bytes | 132096 | 132096 | 143360 | 286720 | 2.17 |
| Tx Size Bytes | 132096 | 132096 | 133120 | 266240 | 2.01 |
| Instructions/threads | 100'000'000 | 400'000'000 | 600'000'000 / 1 thread | 580'000'000 / 2 threads | 2.9 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New Ledger/Tx Ratio would be 1.45, not 2.9? i.e. 580M/400M

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it's 2 * 580 / 400 == 2.9. We have 2 threads in this proposal.


Note, that the close time has increased since SLP-3. Given that the network performance hasn't degraded since then, we propose to relax the threshold for the Soroban apply time to 300ms. The previous threshold of 250ms was very conservative, and a relatively small increase to it shouldn't be able to compromise the network stability.

### Benchmarking with proposed limits
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about adding 400M benchmark numbers in the list below?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants