> Hi,
> I've put the creation of nodes and relationships inside one transaction tx
> and it taked like 2 minutes.
> How can I use the map with key-value when I'm reading from a xml file, and
> therefore I don't know how much properties de node has?

> The number of properties from a node can be dinamic, the first node could
> have 10 properties, the next 15 properties and so on.

> On Thu, Oct 4, 2012 at 1:29 AM, Pablo Ramirez <ramirezsolorz...@gmail.com>wrote:

>> Thank you very mucha Michael, I will to try that.

>> On Thu, Oct 4, 2012 at 1:02 AM, Michael Hunger <
>> michael.hun...@neotechnology.com> wrote:

>>> Pablo,

>>> several things.

>>> #0 your properties file contains a lot of unsuitable values for your
>>> system size if you add the memory sizes you give for memory-mapped-io it is
>>> several times the amount of ram you have, I think for your import you can
>>> just leave off the properties file
>>> #1 you should only have one gdb instance for your import otherwise you
>>> loose your caches in between.
>>> #2 your tx size is too small (just 1 node or rel) you should only commit
>>> (tx.success(); tx.finish(); every 10k nodes/rels and create a new tx)
>>> #3 instead of values and elements list, why not use a map with key-value
>>> ?
>>> #4 don't create the rels with cypher if you have an embedded db instance
>>> at hand use gdb.getNodeById() if you had stored the actual node-id (which
>>> is internal) to your id-mapping somewhere
>>> #5 I doubt that your id lookup works, what you want is either an
>>> auto-index on "id" or a manual index (gdb.index().forNodes("node");
>>> index.add(node,"id",id); and the use index.get("id",id).getSingle() for
>>> lookup
>>> #6 then use node.createRelationship(node2,type) and rel.setProperty()
>>> #7 same problem with tx size in your case it is one tx per relationship
>>> #8 if you want to use cypher you MUST use parameters for your passed in
>>> values (i.e. node-properties or id's to lookup) otherwise cypher has to
>>> parse the query for each execution

>>> HTH

>>> Michael

>>> Am 04.10.2012 um 06:07 schrieb Pablo Ramirez:

>>> Neo version: 1.9SNAPSHOT
>>> 1st computer:
>>> - Core 2 Duo 2.33 GHz
>>> - 6GB RAM DDR2 666MHz
>>> - HD 500 GB SATAII
>>> - Windows 7 and Fedora Installed in the same computer.
>>> - Windows 7 30 minutes, Fedora 16 minutes

>>> 2nd computer:
>>> - Core i5 (4 cores)
>>> - 4GB DDR3 1333MHz
>>> - HD 500 GB SATAII
>>> - Windows7, takes 3 minutes aprox

>>> I'm programming with eclipse IDE
>>> I attached de neo4j configuration file and de code of my application.
>>> What is visualvm and yourkit?

>>> On Wed, Oct 3, 2012 at 5:48 PM, Michael Hunger <
>>> michael.hun...@neotechnology.com> wrote:

>>>> Can you share more details!

>>>> versions used,
>>>> code used,
>>>> configuration of both machines (hardware, OS, and neo4j config)

>>>> probably slow disk (non ssd?)
>>>> how much memory has the other machine?

>>>> did you try to run a profiler (like visualvm or yourkit)?

>>>> etc.

>>>> Michael

>>>> Am 04.10.2012 um 00:25 schrieb Pablo Ramirez:

>>>> > Hi, I'm working in a project in which we have to create graphs from
>>>> reading an xml file, the computer is a Core 2 Duo and 6Gb RAM, running on
>>>> Windows takes 30 minutes and 16 minutes on Fedora,
>>>> > but in other computer Core i5 and Core i7 takes 3 minutes aprox.,
>>>> What can I do to accelerate the process? Why is taking to much time?

>>>> > I tried modifing the configuration file neo4j.properties but it has
>>>> no effect in the creating process. Any idea about that?

>>>> > Thanks.

>>>> > --

>>>> --

>>> --

>>> <GraphDbInstance.java><GraphNodes.java><neo4j.properties>

>>>  --