We have an application where a new graph gets created for new “projects” within the database. There are about 20 vertices and 70 edges, not a massive schema. When we execute the create script, it seems to lock up the database for other graphs/processes. Is this normal? Do we just have to wait for the script to finish or can that be asynchronous in some way?
Hi @fjblau ,
The create script do lock up the database somewhat for other graphs/processes - for instance, you can’t create two graphs in the same cluster at the same time.
I’d say that you should wait until the script is finished to begin operations on other graphs.
In my experience, creating a graph shouldn’t take too long (e.g. 30 seconds on less).
Hope this helps!
Best,
Supawish Limprasert (Jim)
Solution Engineer, TigerGraph
1 Like