Delay in Quote Pricing Updates After AMM Transactions on Self-Hosted Jupiter Instance

[PierreBlouet]

I'm experiencing a delay in quote pricing updates on my self-hosted Jupiter instance. After executing an AMM transaction, the quote pricing takes between 30ms to 100ms to update, instead of updating nearly instantly as expected.

Expected Behavior
Quote pricing should update nearly instantly after an AMM transaction to reflect the latest market data.
Actual Behavior
There is a noticeable delay (30ms to 100ms) before the quote pricing updates following an AMM transaction.
Steps to Reproduce
Set up a self-hosted Jupiter instance with only one market.
Perform an AMM transaction on that market.
Measure the time it takes for the quote pricing to update after the transaction.
Hardware Specifications:
CPU: [ Intel Core i7-9700K]
RAM: [16GB DDR4]
Storage: [ 512GB SSD]
Operating System: [Ubuntu 20.04 LTS]
Possible Cause
Could this delay be due to hardware limitations or configuration issues with the self-hosted setup?

Additional Information
The issue occurs even when only one market is hosted.
Network latency has been checked and appears normal. (less then 1ms)
Any insights or suggestions on how to resolve this delay would be greatly appreciated.

[ZhengYuTay]

it depends on the proximity of your rpc and your server, but 30ms to 100ms sounds quite bad. Is your rpc and server are in the same location?

[PierreBlouet]

Thank you for your response.

I have measured the latency between when a transaction is received via gRPC and when the quote is updated on the self-hosted Jupiter instance. There is no network latency between the measuring program and Jupiter since everything is self-hosted and the RPC is in the same data center.

I used this tool for measuring the latency: mesure_jup_latency

I have conducted tests on both a MacBook M1 and a VPS with 64GB RAM and 16 logical cores, but the results remain the same.

Therefore, the delay seems to be either due to the computation time that Jupiter takes to update its quote or because Jupiter receives the transaction later, even though I am subscribing to transactions via gRPC using the same gRPC server.

Do you have any further suggestions on what might be causing this delay?

[vinerz]

That was a concern of mine. Did you ever find the reason? Was Jupiter also ingesting from yellowstone?