Hi Alan You could reduce the amount of memory per graph, but probably the best idea is the new issue created by Andrey about letting the disk cache to be shared among graphs.
Lvc@ Sent from Mobile device Il 08/gen/2014 18:50 "Alan Miller" <alan.mill...@gmail.com> ha scritto: > Could you explain what you mean by partitioning the data. It's not clear > to me what you mean. > > So far my use case is this. > 1. I'll have a single server instance (@port 2480) which only serves > read-only queries for 3000 graphs. > e.g. > server.database.path = /opt/orientdb/databases > so I'd have > /opt/orientdb/databases/graph_1 ...... > /opt/orientdb/databases/graph_3000 > 2. All graphs are modelling the same type of data but I'll never need to > query data among 2 graphs > 3. All graphs have 1 Vertex type (with 6 properties) and 2 Edge types > (no values). > 4. On average each graph (directory) will be approx 4GB. > 5. Since 3000 graphs @ 4G each is about 12 TB, I guess I may need to run > OrientDB > in distributed mode and spread the 3000 graphs among multiple nodes. > > Regards, > Alan > > On Wednesday, January 8, 2014 1:04:17 AM UTC-8, Artem Orobets wrote: >> >> Hi Alan, >> >> Another benefit of having several graphs is that you can easily move some >> to another server to balance load on servers. >> >> But clearly, there is a restriction, you can't easily implement >> connections between this graphs (e.g. edge from graph A to graph B). >> >> Will a running server detect new graph directories or do I have to restart >>> the server each time a new graph is added? >> >> If you will copy your newly created database to default database >> directory, the server will detect it as soon as you will try to open it. No >> reboot is required. >> >> Best regards, >> Artem Orobets >> >> * Orient Technologiesthe Company behind OrientDB* >> >> >> 2014/1/8 Andrey Lomakin <lomakin...@gmail.com> >> >>> Hi Alan, >>> You can create as many graphs as you need in single Graph instance. >>> It is better than create 3000 graph databases because in case of single >>> storage you will have much efficient RAM usage than in case of 3000 >>> storages. >>> >>> You can tune RAM consumed by memory storage using >>> storage.diskCache.bufferSize it is in megabytes. >>> >>> About your question, there is no limitation on amount of db instances on >>> server. but much better to create several graph instances on single db and >>> use name pattern for partitioning of graph data. >>> For example class_one_partition_one, class_one_partition_two and so on. >>> >>> >>> >>> >>> On Tue, Jan 7, 2014 at 9:02 PM, Alan Miller <alan.m...@gmail.com> wrote: >>> >>>> Is there a limitation on how many graphs an OrientDB instance can serve? >>>> >>>> I'm considering having approx 3000 separate graphs in my server >>>> instance. >>>> >>>> I am building the graphs offline on a daily basis via the Java API and >>>> using >>>> OrentGraphNoTx graph = new OrentGraphNoTx(); >>>> graph.setUseLightWeightEdges(true); >>>> // ..... add vertices >>>> // ..... add edges >>>> graph.commit(); >>>> >>>> Can OrientDB handle so many graphs? >>>> Will a running server detect new graph directories or do I have to >>>> restart >>>> the server each time a new graph is added? >>>> >>>> Thanks >>>> Alan >>>> >>>> -- >>>> >>>> --- >>>> 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 orient-databa...@googlegroups.com. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Andrey Lomakin. >>> >>> Orient Technologies >>> the Company behind OrientDB >>> >>> -- >>> >>> --- >>> 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 orient-databa...@googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- > > --- > 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 orient-database+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- --- 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
