Hi Scott, thanks for your reply!
The VM has 16 GB of RAM. Plenty I'd say, and since we want to store more than ten times than we got now, we have to add new VMs for clustering pretty early. The Data Model is pretty fleshed out right now, we'll have to boil it down at some point in the future. No, we don't store actual binary data in OrientDB, we store, like you said, just references on files. But I thought OrientDBs memory consumption is limited by MAXHEAP="-Xmx512m" anyway? Thanks & best regards, Sebastian On Wednesday, July 29, 2015 at 6:28:46 AM UTC+2, scott molinari wrote: > > I'm a noob at OrientDB too, but I'd ask these questions from experience. > How much RAM does your VM have? If it isn't more than 18.8 GB, then you'll > have an issue with disk I/O (even with a fast NAS). > > Did you add any indexes (which means you'd need considerably more RAM than > 18.8 GB)? > > Is the media you mentioned actually media, like pictures or video? > Although you can store data like that, it would be wise to store it in > something like a distributed file system and just have the locations to the > media stored in the database. Edit: this last note I don't think would be a > cause for your slow performance, but if you can reduce the size of the > database considerably, it might help. > > Scott > -- --- 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.
