Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 1287. (Read 2170889 times)
August 11, 2014, 06:14:48 PM
I've given up on mining for now, it's like playing the lotto solo mining. :/
August 11, 2014, 06:04:16 PM
So I left the plots generating and mining on a couple of VM's overnight, woke up this morning to find that they had all had the same error generating the plots...
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 630517760 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_linux.cpp:2769), pid=8593, tid=139980355077888
Each VM has 16GB of RAM / dual core and they were being generated with ./run_generate.sh 1234567890 1 819100 8191 2
Any ideas?
Incidentally they all crapped out after generating just over 6GB of the plot. Very frustrating. I have to start over now.
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 630517760 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_linux.cpp:2769), pid=8593, tid=139980355077888
Each VM has 16GB of RAM / dual core and they were being generated with ./run_generate.sh 1234567890 1 819100 8191 2
Any ideas?
Incidentally they all crapped out after generating just over 6GB of the plot. Very frustrating. I have to start over now.
not sure ... but i guess it could be the following ...
looks like u use 32bit ... try 500 to 1000 instead of 8191 for memory ...
plots are created in memory and then written to hd, as soon as you reach >1000 in memory you get an exception with 32bit ... right?!
Thanks, I've changed the command line to force it to use the 64bit runtime so that should sort it.
Is there any way to get the generator to resume creating a plot file rather than starting over in the case of a crash?
August 11, 2014, 06:03:27 PM
So I left the plots generating and mining on a couple of VM's overnight, woke up this morning to find that they had all had the same error generating the plots...
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 630517760 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_linux.cpp:2769), pid=8593, tid=139980355077888
Each VM has 16GB of RAM / dual core and they were being generated with ./run_generate.sh 1234567890 1 819100 8191 2
Any ideas?
Incidentally they all crapped out after generating just over 6GB of the plot. Very frustrating. I have to start over now.
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 630517760 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_linux.cpp:2769), pid=8593, tid=139980355077888
Each VM has 16GB of RAM / dual core and they were being generated with ./run_generate.sh 1234567890 1 819100 8191 2
Any ideas?
Incidentally they all crapped out after generating just over 6GB of the plot. Very frustrating. I have to start over now.
First time I've seen that one. The -Xmx4000m switch in the run_generate.sh script is supposed to cap the JVM to 4GB of ram so I don't see how it would get anywhere near high enough for the jvm host to run out of memory. Maybe try a different JVM (oracle or openjdk) if no one has any better ideas.
August 11, 2014, 05:59:32 PM
August 11, 2014, 05:52:35 PM
So I left the plots generating and mining on a couple of VM's overnight, woke up this morning to find that they had all had the same error generating the plots...
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 630517760 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_linux.cpp:2769), pid=8593, tid=139980355077888
Each VM has 16GB of RAM / dual core and they were being generated with ./run_generate.sh 1234567890 1 819100 8191 2
Any ideas?
Incidentally they all crapped out after generating just over 6GB of the plot. Very frustrating. I have to start over now.
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 630517760 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_linux.cpp:2769), pid=8593, tid=139980355077888
Each VM has 16GB of RAM / dual core and they were being generated with ./run_generate.sh 1234567890 1 819100 8191 2
Any ideas?
Incidentally they all crapped out after generating just over 6GB of the plot. Very frustrating. I have to start over now.
not sure ... but i guess it could be the following ...
looks like u use 32bit ... try 500 to 1000 instead of 8191 for memory ...
plots are created in memory and then written to hd, as soon as you reach >1000 in memory you get an exception with 32bit ... right?!
August 11, 2014, 05:40:52 PM
So I left the plots generating and mining on a couple of VM's overnight, woke up this morning to find that they had all had the same error generating the plots...
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 630517760 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_linux.cpp:2769), pid=8593, tid=139980355077888
Each VM has 16GB of RAM / dual core and they were being generated with ./run_generate.sh 1234567890 1 819100 8191 2
Any ideas?
Incidentally they all crapped out after generating just over 6GB of the plot. Very frustrating. I have to start over now.
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 630517760 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_linux.cpp:2769), pid=8593, tid=139980355077888
Each VM has 16GB of RAM / dual core and they were being generated with ./run_generate.sh 1234567890 1 819100 8191 2
Any ideas?
Incidentally they all crapped out after generating just over 6GB of the plot. Very frustrating. I have to start over now.
August 11, 2014, 05:23:07 PM
On one machine I have about 30GB of plot generated and get deadlines anywhere from 20k to 2 million.
On a second machine I have about 200GB of plots, and always get deadlines of 500k to 2 million.
On both machines I get "Error reading file" on every plot file.
On a second machine I have about 200GB of plots, and always get deadlines of 500k to 2 million.
On both machines I get "Error reading file" on every plot file.
August 11, 2014, 05:16:38 PM
The pool situation:
I understand pools are needed, as it is getting very difficult to solo mine. As plots are specific to the account address the coins will go to, this poses a bit of a problem. Pool support will be released in 2 steps:
1. A pool server program will be created that supplies users each a unique address to generate plots for. The user's plots for mining with that pool will only be usable for that pool. This will be released and a pool will be set up hopefully within a few days. It will be very simplistic to try to get it released as soon as possible.
2. Later on, a new client will be released to update the protocol. A user will then be able to announce to the network an address where their mined coins will go to instead of their own. This will allow pool miners to generate plots for themselves, and mine at any pool by setting their mining output address to the pool they want to use.
I understand pools are needed, as it is getting very difficult to solo mine. As plots are specific to the account address the coins will go to, this poses a bit of a problem. Pool support will be released in 2 steps:
1. A pool server program will be created that supplies users each a unique address to generate plots for. The user's plots for mining with that pool will only be usable for that pool. This will be released and a pool will be set up hopefully within a few days. It will be very simplistic to try to get it released as soon as possible.
2. Later on, a new client will be released to update the protocol. A user will then be able to announce to the network an address where their mined coins will go to instead of their own. This will allow pool miners to generate plots for themselves, and mine at any pool by setting their mining output address to the pool they want to use.
Sounds like a plan mate, if you need some testing / development help give me a shout.
On a secondary note, ive been looking through your miners code, I think a ideal setup would be, ssd + fast ish cpu + a smaller gpu, the gpu would do the hashing functions while the cpu is free to continue processing the os and the app, for example, a gpu could be used to generate the plots, while the cpu is free to hash blocks etc thus splitting them and allowing more power without breaking the bank.
The gpu would not have to be a 6970/7970 etc as a small gpu would be utilised better, anyway also in ScoopReader.java from the miner there is a try/catch macro in readFile, a double catch is used, is this even possible in java ?
August 11, 2014, 05:04:42 PM
The pool situation:
I understand pools are needed, as it is getting very difficult to solo mine. As plots are specific to the account address the coins will go to, this poses a bit of a problem. Pool support will be released in 2 steps:
1. A pool server program will be created that supplies users each a unique address to generate plots for. The user's plots for mining with that pool will only be usable for that pool. This will be released and a pool will be set up hopefully within a few days. It will be very simplistic to try to get it released as soon as possible.
2. Later on, a new client will be released to update the protocol. A user will then be able to announce to the network an address where their mined coins will go to instead of their own. This will allow pool miners to generate plots for themselves, and mine at any pool by setting their mining output address to the pool they want to use.
I understand pools are needed, as it is getting very difficult to solo mine. As plots are specific to the account address the coins will go to, this poses a bit of a problem. Pool support will be released in 2 steps:
1. A pool server program will be created that supplies users each a unique address to generate plots for. The user's plots for mining with that pool will only be usable for that pool. This will be released and a pool will be set up hopefully within a few days. It will be very simplistic to try to get it released as soon as possible.
2. Later on, a new client will be released to update the protocol. A user will then be able to announce to the network an address where their mined coins will go to instead of their own. This will allow pool miners to generate plots for themselves, and mine at any pool by setting their mining output address to the pool they want to use.
August 11, 2014, 04:47:07 PM
Hi Guys,
Let's say i have two hdd's and both are used for mining.Is it ok to have just one listenaddress for both wallets? ?
For example: localhost:8125 or do i need to have another instance running on a different port?
The apiserver is listening on 8123. Is this also ok for both instances?
Let's say i have two hdd's and both are used for mining.Is it ok to have just one listenaddress for both wallets? ?
For example: localhost:8125 or do i need to have another instance running on a different port?
The apiserver is listening on 8123. Is this also ok for both instances?
I am also not clear on this. Going to set up plots on a 4TB external and I am not clear on how to set up the second drive. Are we using 2 wallets or can it mine to one wallet?
Thanks in advance. I saw this asked earlier but could not find an answer.
Do you want to create lots of little plots or few big plots?
Also how do you export your private key for BURST?
One large plot and many small ones will run just the same.Also how do you export your private key for BURST?
You just need to backup the passphrase you use in the wallet interface, and put in passphases.txt for mining.
How can we increase our hashrate or chances of finding a block then?
I meant that with the same amount of plots, it doesn't matter how much it's split up. More plots = more mining power though.
August 11, 2014, 04:40:03 PM
Hi Guys,
Let's say i have two hdd's and both are used for mining.Is it ok to have just one listenaddress for both wallets? ?
For example: localhost:8125 or do i need to have another instance running on a different port?
The apiserver is listening on 8123. Is this also ok for both instances?
Let's say i have two hdd's and both are used for mining.Is it ok to have just one listenaddress for both wallets? ?
For example: localhost:8125 or do i need to have another instance running on a different port?
The apiserver is listening on 8123. Is this also ok for both instances?
I am also not clear on this. Going to set up plots on a 4TB external and I am not clear on how to set up the second drive. Are we using 2 wallets or can it mine to one wallet?
Thanks in advance. I saw this asked earlier but could not find an answer.
Do you want to create lots of little plots or few big plots?
Also how do you export your private key for BURST?
One large plot and many small ones will run just the same.Also how do you export your private key for BURST?
You just need to backup the passphrase you use in the wallet interface, and put in passphases.txt for mining.
August 11, 2014, 03:57:07 PM
Hi Guys,
Let's say i have two hdd's and both are used for mining.Is it ok to have just one listenaddress for both wallets? ?
For example: localhost:8125 or do i need to have another instance running on a different port?
The apiserver is listening on 8123. Is this also ok for both instances?
Let's say i have two hdd's and both are used for mining.Is it ok to have just one listenaddress for both wallets? ?
For example: localhost:8125 or do i need to have another instance running on a different port?
The apiserver is listening on 8123. Is this also ok for both instances?
I am also not clear on this. Going to set up plots on a 4TB external and I am not clear on how to set up the second drive. Are we using 2 wallets or can it mine to one wallet?
Thanks in advance. I saw this asked earlier but could not find an answer.
August 11, 2014, 03:08:18 PM
I have got error after starting run_generate.bat
http://prntscr.com/4btyti
What's the problem it should to be?
http://prntscr.com/4btyti
What's the problem it should to be?
Write me in PM the cmd and I will correct it for you!
it is the xmx value, the vm could not create the heap, checkout :
https://bitcointalksearch.org/topic/m.8298798
pretty much lower the -Xmx...m value in the bat file.
August 11, 2014, 03:06:40 PM
i have got 2 now
August 11, 2014, 03:03:28 PM
I have got error after starting run_generate.bat
http://prntscr.com/4btyti
What's the problem it should to be?
http://prntscr.com/4btyti
What's the problem it should to be?
Write me in PM the cmd and I will correct it for you!
August 11, 2014, 02:51:51 PM
Hi Guys,
Let's say i have two hdd's and both are used for mining.Is it ok to have just one listenaddress for both wallets? ?
For example: localhost:8125 or do i need to have another instance running on a different port?
The apiserver is listening on 8123. Is this also ok for both instances?
Let's say i have two hdd's and both are used for mining.Is it ok to have just one listenaddress for both wallets? ?
For example: localhost:8125 or do i need to have another instance running on a different port?
The apiserver is listening on 8123. Is this also ok for both instances?
August 11, 2014, 02:47:56 PM
So... can anyone tell us how the different parameters of the plot generation effect the hashrate of a miner?
There is:
1) the plot size
2) Memory usage
3) number of cores
There is:
1) the plot size
2) Memory usage
3) number of cores
August 11, 2014, 02:42:45 PM
Any places to exchange or trade?
August 11, 2014, 02:41:22 PM
Do you want to create lots of little plots or few big plots?
Also how do you export your private key for BURST?
Also how do you export your private key for BURST?
the private key is the passphrase from here : pocminer_v1/passphrase.txt
August 11, 2014, 02:37:48 PM
i knew there was a reason i was waiting to use the rest of my amazon vps credit.
Jump to: