:D I know I wrote it, but I didn't have good answers yet at that moment and I had to evaluate the feasibility of my project, so I wanted to ask OrientDB folks too to understand how things are working on the db side, to know if there was a problem in BaasBox implementation, if there was space to make things better in the future, etc.
Now on BaasBox group it's been given an amazing answer, so I guess the topic is closed ;) For anybody in the future interested in the answer, giastfader responded here: https://groups.google.com/forum/#!topic/baasbox/FwD-zFE5CeE [d] Il giorno giovedì 5 marzo 2015 01:26:07 UTC+1, Claudio ha scritto: > > Hi, > please read > https://groups.google.com/d/msg/baasbox/FwD-zFE5CeE/yd69EOdlD-IJ > You posted a similar question to the BaasBox group too. > > > Il giorno mercoledì 4 marzo 2015 20:22:59 UTC+1, Davide Neri ha scritto: >> >> Ok, I need to review what I wrote cause doing further testing something >> happened. >> After rebooting the droplet the DB is on, the size dropped to a much >> better size. Seems like it was cache taking up space. >> Also, every time a new vertex is made the dashboard of BaasBox is >> reporting that the dimension of the overall database increases of the 5KB+, >> but the dimension of the collection the vertex increases of only >> 400Bytes...so of the amount. >> >> After rebooting the "database size" drops but not as much to reach the >> "collection size" ...each vertex on the "database size" weights around 1KB. >> And each edge around 0.85KB. >> Are these sizes good or is there still something different from the way >> OrientDB usually works? >> >> Thank you very much >> >> [d] >> >> >> Il giorno mercoledì 4 marzo 2015 18:41:52 UTC+1, Davide Neri ha scritto: >>> >>> I started to use OrientDB through BaaSBox. I'm making some tests to >>> quantify the resources I'll need in the future in the project I'm working >>> on. >>> I realized that, after the creation of 1000 vertices, each one with a >>> JSON content of around 400 Bytes, the db size increased of 6.5 MB. That >>> means that each vertices size on the hard disk is 6.5 KB, even if I'm >>> storing only 400 Bytes of data. >>> Then I tried the same with edges, and after the creation of 1000 edges >>> the database increased of 10 MB. That means that each edge size on the hard >>> disk is of 10 KB. >>> >>> Are these data right? >>> Are these the usual sizes for OrientDB vertices and edges, or is the >>> size due to the way BaaSBox is using it? >>> >> -- --- 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.
