-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chores/213 ordinals readme #218
Conversation
The Ordinal Service Client is the primary method for checking inscriptions on UTXOs. It connects directly to a running instance of the [Ordinal Service](https://github.com/ordinals/ord). | ||
|
||
### Verification Process | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could u add the endpoint that we are using from ordinal service?
Also worth adding some of the load test result from @filippos47
i.e
Did a stress test with the latest 450k BTC txs (100 blocks) on a single ord instance with 5k concurrent users:
Latencies
50th percentile: 0.5 - 2 s
95th percentile: 5 - 6.5 s
RPS
peak: 1.1k RPS
sustained >800 RPS for 15 mins
Resources-wise, the bare-metal host barely felt any effect
and lower rps (100 rps) has better p95 performance latency around 300ms
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't seen service maintainers including performance data (eg RPS / latencies) in READMEs. These data can greatly vary depending on network / compute.
If you still feel it's helpful, I'll write something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the endpoint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't have benchmark, so i think have something to give a rough idea is better than nothing.
at least we know it's ~300ms level for 100 rps, not 30s 😄
Closing this PR. it will be address in other PR |
No description provided.