Re:Ask HN: What was your experience using a graph database?
by chadcmulligan on Tuesday January 01, 2019 @01:44AM
(#18799275)
It depends on the structure of the DB - 6.5GB is large if its attributes, if its documents then not so much. If its an index of documents then a different problem. Access patterns matter to. Like if its a 6.5 GB database that stores OLTP data, then yes thats large. If its a history of document modifications then probably small. If its historical data for a data cube sort of app, then its pretty small, I'd say tiny - I've worked on ones that get into the TB's.
Re:Ask HN: What was your experience using a graph database?
by reaperducer on Tuesday January 01, 2019 @11:31AM
(#18800790)
It's all attributes; no documents being stored. About 2m records.
Re:Ask HN: What was your experience using a graph database?
by chadcmulligan on Tuesday January 01, 2019 @03:51PM
(#18802275)
So thats a bit over 3k per record. Forgive my curiosity but whats the application domain? Thats a lot of info per record.
How does one know if it's time to migrate to a graph database?
Right now I have a large (6.5GB) database that I have to sometimes work with, and the queries are getting more complex as more features are added to the project.
Right now the data is stored in MySQL, but to get anything interesting out of it requires multiple queries and then sifting through the data later. It all seems cumbersome.