Retrieving edges from KB takes too long about fasten HOT 5 CLOSED

I am not sure why you need to create an intermediate view. What is wrong with a simple join?

select e.src, e.target 
   from edges e 
    join callables c on e.src = c.id
    join modules m on m.id = c.module_id 
....
--- other join conditions

If you want to get the callables for 2 edges (not just the edge ids), then it is 2 joins

select c1.fasten_uri, c2.fasten_uri 
   from edges e
    join callables c1 on e.src = c1.id
    join callables c2 on e.target = c2.id
    join modules m on m.id = c1.module_id 
....

with the appropriate indices in place (and given enough memory) it should not be too slow

from fasten.

@gousiosg Are there any reasons why we wouldn't use graph database for it?

from fasten.

Yes, the graph DB only contains ids, which will need to be resolved against the callables table as well

from fasten.

I mean let's first try the simple solution and see if it works and then we can think of more elaborate schemes

from fasten.

I am not sure why you need to create an intermediate view. What is wrong with a simple join?

Nothing, my bad. Sorry for not seeing the already-existing multicolumn B-Tree index on edges.source_id and edges.target_id. If the response body is correct (edges.*), then a single join will do the job. Sorry for the hassle.

from fasten.