Re: [Neo] Dijkstra search on a big graph

2010-02-22 Thread Anton Popov
Hello,

Cool, let me know if there will be any changes.

On 17 February 2010 15:15, Johan Svensson jo...@neotechnology.com wrote:

 Hi,

 Just wanted to say that I have successfully reproduced the warning
 messages and we will have a look at this.

 -Johan

 On Tue, Feb 9, 2010 at 11:17 AM, Anton Popov popov.ua.w...@gmail.com
 wrote:
  Hello johan,
 
  apo...@mars:~$ java -version
  java version 1.6.0_16
  Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
  Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
 
  apo...@mars:~$ uname -svr
  Linux 2.6.28-18-generic #59-Ubuntu SMP Thu Jan 28 01:40:19 UTC 2010
 
  On 8 February 2010 21:38, Johan Svensson jo...@neotechnology.com
 wrote:
 
  Hi Anton,
 
  Sounds like you can reproduce this problem? If so I would definitely
  like to have a look at it.
 
  Btw, what JVM and Linux kernel version are you running?
 
  -Johan
 
  On Mon, Feb 8, 2010 at 3:59 PM, Anton Popov popov.ua.w...@gmail.com
  wrote:
   Hello Johan,
  
   Thanks for your answer  see my answers below:
  
   On 8 February 2010 11:15, Johan Svensson jo...@neotechnology.com
  wrote:
  
   Hi,
  
   How large heap have you set? I see that you have allocated 3G for
   memory mapping that leaves about 512M max left for heap size since OS
   (and other on OS processes) needs some memory.
  
  
   Yes, I've set 3G for memory mapping, but application allocated only
 1.8G,
   that leaves enough memory for OS, imho. Anyway, changing parameters of
   property file 1G - 500M (so max allocated memory should be 1.5G
 instead
  of
   3G) changes nothing. I've got the same exceptions.
  
  
   I have not seen this stacktrace on Linux (used to happen a lot on
   32-bit windows versions since the 2G continuous map limit really
   wasn't 2G).
  
  
   I use 64-bit PC if this matters.
  
   Try lower nodestore memory mapped settings (check how large file is,
   should not be 1GByte?) and see if that helps.
  
  
   As described above - using any setting values has no influence on my
 app.
  To
   be sure, I can say that small routes are found pretty fine, without
 any
   exceptions.
   What file you are talking about?
 ___
 Neo mailing list
 User@lists.neo4j.org
 https://lists.neo4j.org/mailman/listinfo/user




-- 
Best regards,
Popov Anton
___
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user


Re: [Neo] Dijkstra search on a big graph

2010-02-09 Thread Anton Popov
Hello johan,

apo...@mars:~$ java -version
java version 1.6.0_16
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)

apo...@mars:~$ uname -svr
Linux 2.6.28-18-generic #59-Ubuntu SMP Thu Jan 28 01:40:19 UTC 2010

On 8 February 2010 21:38, Johan Svensson jo...@neotechnology.com wrote:

 Hi Anton,

 Sounds like you can reproduce this problem? If so I would definitely
 like to have a look at it.

 Btw, what JVM and Linux kernel version are you running?

 -Johan

 On Mon, Feb 8, 2010 at 3:59 PM, Anton Popov popov.ua.w...@gmail.com
 wrote:
  Hello Johan,
 
  Thanks for your answer  see my answers below:
 
  On 8 February 2010 11:15, Johan Svensson jo...@neotechnology.com
 wrote:
 
  Hi,
 
  How large heap have you set? I see that you have allocated 3G for
  memory mapping that leaves about 512M max left for heap size since OS
  (and other on OS processes) needs some memory.
 
 
  Yes, I've set 3G for memory mapping, but application allocated only 1.8G,
  that leaves enough memory for OS, imho. Anyway, changing parameters of
  property file 1G - 500M (so max allocated memory should be 1.5G instead
 of
  3G) changes nothing. I've got the same exceptions.
 
 
  I have not seen this stacktrace on Linux (used to happen a lot on
  32-bit windows versions since the 2G continuous map limit really
  wasn't 2G).
 
 
  I use 64-bit PC if this matters.
 
  Try lower nodestore memory mapped settings (check how large file is,
  should not be 1GByte?) and see if that helps.
 
 
  As described above - using any setting values has no influence on my app.
 To
  be sure, I can say that small routes are found pretty fine, without any
  exceptions.
  What file you are talking about?
 
 
  Regards,
  -Johan
 
  --
  Best regards,
  Popov Anton
 ___
 Neo mailing list
 User@lists.neo4j.org
 https://lists.neo4j.org/mailman/listinfo/user




-- 
Best regards,
Popov Anton
___
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user


Re: [Neo] Dijkstra search on a big graph

2010-02-08 Thread Johan Svensson
Hi,

On Fri, Feb 5, 2010 at 6:36 PM, Anton Popov popov.ua.w...@gmail.com wrote:
 Hello all,

 I'm still doing my tests on Neo4J. I've imported some data to Neo4J database
  trying to search a shortest path search using Dijkstra implementation from
 neo4j-graph-algo package.
 As a result - I get exceptions  hanged application - can anyone help me to
 solve the problem?

 I've packed the bundle, containing Java code, system output (with
 Exceptions), neo4j.properties and results of top command. It's available
 here:
 https://docs.google.com/leaf?id=0Bx7diqqg3SSaYzMzZjU1ZGUtNjhjOS00MDg1LWFhYzItOWY0YjU5MTRlODdmhl=en
 Please forgive me many System.out prints - that's just an test code to be
 introduced to the system, it's features  performance.

 After the last Exception, written to the output application seems to hang.
 Used memory is 1848m during that moment.
 My environment is:
  - Ubuntu, 4GB of RAM.
  - Before test starts, top shows that I have 3.4GB of RAM non-used. So
 almost no other applications run.
  - I'm using following Neo4J versions:
 ...
 The Exceptions actually are:
 ...
 Caused by: java.io.IOException: Invalid argument
    at sun.nio.ch.FileChannelImpl.truncate0(Native Method)
    at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:728)
    at
 org.neo4j.kernel.impl.nioneo.store.MappedPersistenceWindow.init(MappedPersistenceWindow.java:53)
    ... 15 more

How large heap have you set? I see that you have allocated 3G for
memory mapping that leaves about 512M max left for heap size since OS
(and other on OS processes) needs some memory.

I have not seen this stacktrace on Linux (used to happen a lot on
32-bit windows versions since the 2G continuous map limit really
wasn't 2G).

Try lower nodestore memory mapped settings (check how large file is,
should not be 1GByte?) and see if that helps.

Regards,
-Johan
___
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user


Re: [Neo] Dijkstra search on a big graph

2010-02-08 Thread Anton Popov
Hello Johan,

Thanks for your answer  see my answers below:

On 8 February 2010 11:15, Johan Svensson jo...@neotechnology.com wrote:

 Hi,

 How large heap have you set? I see that you have allocated 3G for
 memory mapping that leaves about 512M max left for heap size since OS
 (and other on OS processes) needs some memory.


Yes, I've set 3G for memory mapping, but application allocated only 1.8G,
that leaves enough memory for OS, imho. Anyway, changing parameters of
property file 1G - 500M (so max allocated memory should be 1.5G instead of
3G) changes nothing. I've got the same exceptions.


 I have not seen this stacktrace on Linux (used to happen a lot on
 32-bit windows versions since the 2G continuous map limit really
 wasn't 2G).


I use 64-bit PC if this matters.

Try lower nodestore memory mapped settings (check how large file is,
 should not be 1GByte?) and see if that helps.


As described above - using any setting values has no influence on my app. To
be sure, I can say that small routes are found pretty fine, without any
exceptions.
What file you are talking about?


 Regards,
 -Johan
 ___
 Neo mailing list
 User@lists.neo4j.org
 https://lists.neo4j.org/mailman/listinfo/user




-- 
Best regards,
Popov Anton
___
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user