Becoming a dedicated Node with the cloud symbol

[ben]

i am running for 4 days 0.3.19.e now
at the moment 1300 peers connected

Everything stable

java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

64 Bit Linux - 2GIG RAM - Debian


NXT started with: java -Xms1024m -Xmx1536m -jar start.jar

[JohnyCrypt]

I'm using OpenJDK. I wonder if that is part of the problem. I'm going to switch one of the nodes over and see if it behaves better.

Update:
The client refused to start with OpenJDK and abctc's tuning on a DigitalOcean 512mb droplet. I would receive "Error during initialization of VM. Too small initial heap." Oracle JRE works without issue. Hopefully this fixes my stability issues. I'm switching over all my nodes to Oracle's release.

Link: https://bitcointalk.org/index.php?topic=345619.msg3947607#msg3947607

Startup string:

Code: [Select]

java -Xms448m -Xmx480m -jar start.jar


[DiCE1904]

i am running for 4 days 0.3.19.e now
at the moment 1300 peers connected

Everything stable

java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

64 Bit Linux - 2GIG RAM - Debian


NXT started with: java -Xms1024m -Xmx1536m -jar start.jar

what did you set your peers # too and all that?


also did anyone see that picture i posted earlier of my cmd going crazy?