Hi Simon, If you use SQL to select the book and view its publisher do you get the same OOM exception?
Thanks, -Colin On Thursday, July 9, 2015 at 1:56:32 AM UTC-5, Simon White wrote: > > I am getting a heap space error in orientdb studio when I navigate a > particular edge in the studio graph view and I have no idea why, I thought > these sort of traversals would be really fast... > > My scenario: > > 1. I have 2 million 'books' in a cluster, I select a particular one in the > graph... 'Select from #2:123' and see the vertex bubble > > 2. The given book has one (and only one) edge to another vertex > 'publisher' so I navigate that by clicking the 'out' vertex, however the > publisher never appears 'Java out of heap' > > There are only 2000 publishers in the db, but (I think this is the part > that is causing the problem) a given 'publisher' has out edges to several > thousands of books. I know that selecting a publisher and trying to view > all edges to books would be silly (and may well result in out of memory) > but surely the inverse - selecting a book and trying to view its single > publisher - should be fast and efficient?.. The edge goes from book to > publisher after all. > > What have I missed? -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
