3 ms·
I'm not sure if you are serious or joking. "6 degrees of separation" is the famous radius for how many steps are needed such that everyone is connected. https
by eurg 2y ago
I'm not sure if you are serious or joking. "6 degrees of separation" is the famous radius for how many steps are needed such that everyone is connected.
https://en.wikipedia.org/wiki/Six_degrees_of_separation https://en.wikipedia.org/wiki/Six_degrees_of_separation
- demaga 2y agoExcept that it wasn't about people at all? I was just referring to a _type_ of query
- ffsm8 2y agoWhat kind of data was it, of I may ask? Graph databases have a very narrow usecase, and it's almost always in relation to people - at least ime. Though the data type isn't really important for the performance question, the amount of data selected is. So a 6-level depth graph of connections that only connect 2-3 entities would never get into performance issues. You'd be able to go way beyond that too with such a narrow window. (3 entity Connections on 6 level join would come out to I believe ~750 rows) If you're modeling something like movies instead, with >10 actors per production you're looking at millions of rows.
- derefr 2y agoNetwork analysis of financial transactions to detect "layering" (onion-routed money laundering) paths, probably.
- zaphirplane 2y agoToo funny, enjoy the vote