Our production environment continuously writes to Dgraph, and the write pressure is quite high. When the batch size is large, Dgraph often gets stuck at the WaitForTs function. Would it be possible to mitigate this issue by caching the previous startTS value and using it as a query parameter? (Our r…

You can just reuse old start ts, and it should work. However, using old start ts could cause issues. You could use zero’s api to get a timestamp and then keep using it.

Optimizing Dgraph Write Performance with Cached startTS

Users Dgraph

matthewmcneely (Matthew McNeely) March 18, 2025, 4:12pm 7

Also, if you’re trying to unblock the reads, I think an RO+best-effort query would by-pass the wait for the TS. Right @harshil_goel?

Topic		Replies	Views
Lifetime of startTs Dgraph	9	496	August 13, 2020
Extremely slow Oracle().WaitForTs() during mutation Dgraph	10	383	June 10, 2021
In the cluster, the query returns the start_ts never changes Dgraph kind:question , dgraph	4	456	January 7, 2021
Dgraph queries without besteffort flag timing out Dgraph kind:question , dgraph , status:accepted , ticket:created	17	898	April 15, 2021
Start_ts not being cleared before postings are written to disk Dgraph status:accepted , kind:bug , ticket:created	1	516	August 19, 2020

Optimizing Dgraph Write Performance with Cached startTS

Related topics