Closed kostja closed 6 years ago
Why we can not just create a fiber and kill it by timeout?
The first implementation can be the following:
query_timeout
variable to query context at the beginning of an execution.fiber.time64() < query_timeout
on each itaration.Cons:
fiber.time64()
is fastDisses:
fiber.timeout64()
is updated on yields only and in case of local memex will not change during all query execution. Key points:
clock.monotonic64()
because it is fast and it changes without yieldsaccessor.new()
, and move to tgql.compile
after #59
Allow to interrupt execution of a complex query when a timeout expires.