Hi Luca,
I tested this and now get 0.24sec average inserts, which is the fastest
distributed performance I've experienced yet.
There still seems to be communication with the remote node before releasing
the client though.
Regards,
- Ben
On Wednesday, September 24, 2014 1:24:23 AM UTC+2, Lvc@
Hi Ben,
I found a bottleneck in Hazelcast:
https://github.com/hazelcast/hazelcast/issues/3661.
I could put a queue between ODistributedStorage and HZ. Let me try it now.
Soon a new push.
Lvc@
ᐧ
On 24 September 2014 10:59, vogt@gmail.com wrote:
Hi Luca,
I tested this and now get 0.24sec
I see there is a driver OrientDB-NET.binary but its very old and not any
more maintained I feel.
--
---
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
Would be really nice if someone could tell me how to use that since there
is no documentation out there.
I know it's still experimentell but why not test it before the final
release is there. So if anyone knows how to use please share. Thanks.
Am Freitag, 19. September 2014 19:41:06 UTC+2
Hi Vlad
I would propose you looked at this as two questions. The second question is
easy:
What would be if I do
new OrientGraphFactory(remote:orientdb.node1.com/TestDistributedDatabase,
username, password).getTx()
?
This way I connect specific node and as I understand can play with data on
Hi guys,
I've some updates. Using an queue in the middle improved performance.
Furthermore I've extended the asynchronous also to transactions.
Please could you re-test last version 2.0-M2-SNAPSHOT?
Lvc@
ᐧ
On 24 September 2014 11:31, Luca Garulli l.garu...@gmail.com wrote:
Hi Ben,
I found
Hi,
I'd like to update this thread too by trying last 2.0-M2-SNAPSHOT where now
it's asynchronous apart form Hazelcast.
Lvc@
ᐧ
On 9 September 2014 11:24, vogt@gmail.com wrote:
So here is my final report...
We have scoured all the available docs and come to the conclusion that
OrientDB
There is a fork from that repository that is now actively maintained.
https://github.com/workshare/OrientDB-NET.binary
I am not related to that repository in any way, but found out about it a
few days ago.
On Wednesday, 24 September 2014 13:03:29 UTC+3, Sherry Ummen wrote:
I see there is a
On 24 Sep 2014, at 16:31, Luca Garulli l.garu...@gmail.com wrote:
Hi guys,
I've some updates. Using an queue in the middle improved performance.
Furthermore I've extended the asynchronous also to transactions.
Please could you re-test last version 2.0-M2-SNAPSHOT?
FYI, I get the following
Hi Stuart,
You're right. I've applied your fix, pushed, deployed on sonatype as
2.0-M2-SNAPSHOT.
Lvc@
ᐧ
On 24 September 2014 18:17, Stuart McCulloch mccu...@gmail.com wrote:
On 24 Sep 2014, at 16:31, Luca Garulli l.garu...@gmail.com wrote:
Hi guys,
I've some updates. Using an queue in the
Hi,
I get this error - any help on this?
This is the code that is causing the exception:
package test;
import java.text.SimpleDateFormat;
import java.util.Date;
import java.util.List;
import java.util.concurrent.*;
import com.orientechnologies.orient.core.sql.query.OSQLSynchQuery;
import
Many thanks to Luca for seriously looking into this matter.
I can report that inserts and deletes are blazingly fast compared to what
was previously.
Only connects and updates seem to still lag behind.
Following is an overview issuing commands over the binary interface:
*dserver.sh* with
And as such, I would like to retract my previous disgruntled statement.
As of the latest 2.0-M2-SNAPSHOT, OrientDB indeed supports *true*
asynchronous replication.
Regards,
- Ben
On Wednesday, September 24, 2014 5:32:45 PM UTC+2, Lvc@ wrote:
Hi,
I'd like to update this thread too by trying
Hi,
You should follow https://github.com/orientechnologies/orientdb/issues/2840
On Wed, Sep 24, 2014 at 10:57 PM, iinsel...@gmail.com wrote:
Hi,
I get this error - any help on this?
This is the code that is causing the exception:
package test;
import java.text.SimpleDateFormat;
import
14 matches
Mail list logo
