Hi, please try 1.7-rc1 or 1.7-rc2-SNAPSHOT. Furthermore don't use remote but rather plocal URL directly.
Lvc@ On 20 February 2014 19:33, tia <[email protected]> wrote: > > Hi, > Any updates on this? Been struggling with this problem also. I test > loaded an RDF/XML file with 48631 triples and the total time to complete is: > > TOTALTIME (ms): 971055 > > And this is a load onto an empty database. When i load a file that has > nodes with less edges, timing is very fast . > > Here's my code for loading and the test data file if that would help. > I'm running orientdb-server-1.7-SNAPSHOT . > > > > public void loadRDFFile_OrientGraphNoTx( > String remoteDbsUrl, String remoteDbsUser, String remoteDbsPwd > , > String inputFile, String baseURI, String inputFormat) { > > Orient.instance().registerEngine(new OEngineRemote()); > > OrientGraphNoTx graph = new OrientGraphNoTx(remoteDbsUrl,remoteDbsUser > , remoteDbsPwd); > graph.getRawGraph().declareIntent(new OIntentMassiveInsert()); > > Sail s = new GraphSail<OrientGraphNoTx>(graph); > SailGraph sailGraph = new SailGraph(s); > > Long curr=System.currentTimeMillis(); > System.out.println((new Timestamp((new java.util.Date()).getTime > ())) + "|STARTTIME: "+ curr); > try { > sailGraph.loadRDF( > new FileInputStream(inputFile), > baseURI, > inputFormat, > null); > System.out.println("TOTALTIME: "+(System.currentTimeMillis()- > curr)); > > } catch (FileNotFoundException e) { > e.printStackTrace(); > } catch (java.lang.RuntimeException e2) { > System.out.println("DATAFILE FAILED LOADING: "+ inputFile); > e2.printStackTrace(); > > } finally { > sailGraph.shutdown(); > graph.shutdown(); > } > } > > > Tia > > > > On Thursday, October 31, 2013 12:51:58 PM UTC-7, Jan Drake wrote: >> >> Luca, >> >> Looks like Darren didn't get a resolution for insert speeds with >> OrientDB. I found this: http://blog.euranova.eu/wp- >> content/uploads/2013/10/an-empirical-comparison-of-graph-databases1.pdf >> >> I'm seeing very similar problems with 1.5 and inserting into a graph with >> about five vertex classes and 7 edge classes but with fairly high >> cardinality of edge instances to vertex instances. >> >> What should we expect from OrientDB in terms of insertion speed? >> >> >> Jan >> >> >> On Wednesday, October 30, 2013 5:54:02 PM UTC-7, Jan Drake wrote: >>> >>> Darren, >>> >>> Did you get a resolution on this? I'm seeing similar issues with 1.5 >>> and 50-150 edges. >>> >>> On Friday, February 15, 2013 1:59:34 PM UTC-8, [email protected] wrote: >>>> >>>> Hi All, >>>> >>>> Has anyone come up with a preferred solution for this? Using tinkerpop >>>> 2.2.0 and orient 1.3 i have tried using 4 different approaches >>>> (GraphMLReader, BatchGraph<OrientGraph>, OrientBatchGraph and >>>> OGraphDatabase directly) to load a graph with about 100K vertex and 200K >>>> edges and is structured as 100 trees that go 4 levels deep. This load is >>>> taking over a minute for all methods ranging from 62 seconds to 78 >>>> seconds. There is not that much difference in time so I'm assuming the >>>> slow down is due to some configuration issue and not the specific api used >>>> but I'm just not seeing it. This solution will need to scale to about 10 >>>> to 20 million vertex and 30 to 40 million edges in production and run >>>> regularly. I have attached the 4 classes implementing the load. >>>> >>>> Any feed back would be greatly appreciated. >>>> >>>> Thanks >>>> Darren >>>> >>>> -- > > --- > 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/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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
