Thanks for the replies so far guys

Well why not using the Java API or the ETL tool to import huge amounts of 
> data?
>

We could try that out for the initial dump of data, but in production we 
will likely see bursts of over 1000 inserts a second. I just wanted to see 
how fast it could actually insert and thats how I ran into this 

Have you tried 'declare intent massivewrite'? - 
> http://www.orientechnologies.com/docs/2.0/orientdb.wiki/Console-Command-Declare-Intent.html
>  
> <http://www.google.com/url?q=http%3A%2F%2Fwww.orientechnologies.com%2Fdocs%2F2.0%2Forientdb.wiki%2FConsole-Command-Declare-Intent.html&sa=D&sntz=1&usg=AFQjCNFyRqEchlr0gYWXZ0S2hdjeugA1Yg>
>

Not yet, I was not sure how to do this from the nodejs client. Can i just 
run it in a SQL statement  prior to my insert loop ? Does it effect all 
clients on the database or just my connection?

*ASYNCHRONOUS_NOANSWER* means it doesn't wait for the response, but it's 
executed asynchronously.

Please could you test this mode on last OrientDB 2.0-M2-SNAPSHOT?


- Is this roughly equivilant to running with {writeConcern:0 } in mongodb ( 
if the document doesnt save, its lost) ?
- Ive only been using orient for a day now, with the nodejs client oriento, 
how would I pass those additional parameters with the 

Forgive me for my noobness, but I'm not sure how exactly to run a insert 
command with those new parameters from the nodeJS client. 
var imp = { ts: "foo", id:"bar", ... }
dbclass.create(imp).then(function (record) {
...
}

Finally, it seems like everytime I try and save a document it seems like 
its trying to save it as a graph now, even though I select document DB

db:
      { sessionId: 19,
        name: 'imps',
        server: [Object],
        type: 'graph',
        ...
      }

On Tuesday, September 23, 2014 12:38:31 PM UTC-4, Lvc@ wrote:
>
> Hi guys,
> I've just pushed to "develop" branch this fix:
>
> https://github.com/orientechnologies/orientdb/issues/2833
>
> To enable true asynchronous operations also in ODistributedStorage. 
> Example:
>
> database.save(document, 
> *ODatabaseComplex.OPERATION_MODE.ASYNCHRONOUS_NOANSWER*, false, null, 
> null);
>
> *ASYNCHRONOUS_NOANSWER* means it doesn't wait for the response, but it's 
> executed asynchronously.
>
> Please could you test this mode on last OrientDB 2.0-M2-SNAPSHOT?
>
> Lvc@
>
>
>
> On 23 September 2014 14:20, Emrul Islam <[email protected] <javascript:>> 
> wrote:
>
>> Have you tried 'declare intent massivewrite'? - 
>> http://www.orientechnologies.com/docs/2.0/orientdb.wiki/Console-Command-Declare-Intent.html
>>
>> I haven't profiled orientdb in a distributed config yet but its on my 
>> task list.
>>
>>
>> On Tuesday, September 23, 2014 4:07:42 AM UTC+1, Luke Rossy wrote:
>>>
>>> Hi, I am new to OrientDB and I have some questions regarding write 
>>> performance. 
>>>
>>> We used a Document based DB, and then tried to dump a sample set of data 
>>> and start playing with it to learn more about OrientDB
>>>
>>> We started with the 1.7.9 release and set it up on two servers with the 
>>> following specs.
>>>
>>> Debian 7
>>> 8GB DDR3-ECC Un-Buffered RAM
>>> 1x 1TB HDD
>>> Xeon E31230 V2 (3.30GHz)
>>> Java 7
>>>
>>> Then, on another server on the same LAN, we had a nodejs script read 
>>> from a flat file, and used the nodejs client (
>>> https://github.com/codemix/oriento 
>>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fcodemix%2Foriento&sa=D&sntz=1&usg=AFQjCNEHi0Don9lTDapdaQjGpasXYa3ePQ>)
>>>  
>>> to insert the data row by row into OrientDB. 
>>>
>>> Our script was maxed out at ~350 inserts a second. 
>>>
>>> Then, we installed 2.0-M1 and did the exact same test, and the write 
>>> performance went up, but only to 600 inserts / second
>>>
>>> Finally, I killed the one of the two nodes, and then the performance 
>>> rose to 3000 inserts/sec. 
>>>
>>> Are there any configuration options I should be tuning for write heavy 
>>> databases? 
>>>  
>>> I have already tried Dstorage.diskCache.bufferSize but there was no 
>>> significant change. 
>>> I have also changed writeQuorum = 1 (even though that was against your 
>>> recommendation in the docs) 
>>>
>>> Why is there such a massive difference between distributed and stand 
>>> alone performance? What can I do to minimize this?
>>>
>>>
>>> Thank you 
>>>
>>>
>>>
>>>  -- 
>>
>> --- 
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
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.

Reply via email to