|
SpeedDemon13
|
 |
August 15, 2014, 12:00:19 PM |
|
If anyone is interested, the conclusion of my test to see if I could speed up plot generation by farming it out using cluster/cloud computing is: Yes it can be done, but it is probably not worth it. This is what I did using Amazon EC2... First I created a single instance (2 core) to act as the server for the plot storage and also act as the wallet server / miner. This instance had a 1TB Elastic Block Store volume attached to it (1TB is max EBS volume size on AWS). I made this volume available to the network using NFS I then created a "plot generator" instance with much higher CPU capacity (C3.xlarge 8 core). I mounted the shared volume so it appeared like a local disk and started creating 10GB plots I then created a few scripts so that upon startup the instance would auto-mount the NFS volume, figure out what the last used nonce range was, and start mining from the next 10GB plot Finally, I created an image of this instance and spooled up 100 more instances like it (spot rates, nice and cheap). To begin with it all looked great but I soon hit the bandwidth limit of the instance I was using as the server. In essence the server didn't have enough network bandwidth to cope with all of the data being copied to it. This restricted plot creation to a little over 100GB / hour. Changing the instance type of the server instance to one with a "high" network performance got this up to around 400 GB/hour. If I had have left it running I would have created all 1 TB of plots in 2.5 hours, at a cost of around $20. This could have been repeated or even parallelized to create several 1TB volumes full of plots in a relatively short amount of time. After all the fiddling about getting it working, I spent around $70 testing this stuff out, only to conclude it was too much hassle. And as OP said earlier, the cost of EBS storage on AWS is too high to make this a viable long term mining option. That said, had I have done all of this on day one, I would have scaled the process out and had 10TB+ up within the first few hours and dominated the mining. Good to know I have the process licked for the next PoC coin  Unfortunately I STILL don't have any BURST as I don't have any spare capacity at home so haven't been able to mine at all  So if anyone would like to donate some coins to offset the cost of testing all of this, my address is BURST-WADY-CBZE-HSJU-2NH5G Many thanks! At $70 per day, that's $2100 per month. You can nearly buy a mobo, a used 6/12 core (12/24 threads) Intel cpu, Ram and some HDD's for that price, give or take....LOL |
CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911 |
|
|
|
|
|
|
|
|
|
The trust scores you see are subjective; they will change depending on who you have in your trust list. |
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
tricass
Sr. Member
 Offline
Activity: 394
Merit: 250
Crypto enthusiast
|
|
August 15, 2014, 12:00:45 PM |
|
If anyone is interested, the conclusion of my test to see if I could speed up plot generation by farming it out using cluster/cloud computing is: Yes it can be done, but it is probably not worth it. This is what I did using Amazon EC2... First I created a single instance (2 core) to act as the server for the plot storage and also act as the wallet server / miner. This instance had a 1TB Elastic Block Store volume attached to it (1TB is max EBS volume size on AWS). I made this volume available to the network using NFS I then created a "plot generator" instance with much higher CPU capacity (C3.xlarge 8 core). I mounted the shared volume so it appeared like a local disk and started creating 10GB plots I then created a few scripts so that upon startup the instance would auto-mount the NFS volume, figure out what the last used nonce range was, and start mining from the next 10GB plot Finally, I created an image of this instance and spooled up 100 more instances like it (spot rates, nice and cheap). To begin with it all looked great but I soon hit the bandwidth limit of the instance I was using as the server. In essence the server didn't have enough network bandwidth to cope with all of the data being copied to it. This restricted plot creation to a little over 100GB / hour. Changing the instance type of the server instance to one with a "high" network performance got this up to around 400 GB/hour. If I had have left it running I would have created all 1 TB of plots in 2.5 hours, at a cost of around $20. This could have been repeated or even parallelized to create several 1TB volumes full of plots in a relatively short amount of time. After all the fiddling about getting it working, I spent around $70 testing this stuff out, only to conclude it was too much hassle. And as OP said earlier, the cost of EBS storage on AWS is too high to make this a viable long term mining option. That said, had I have done all of this on day one, I would have scaled the process out and had 10TB+ up within the first few hours and dominated the mining. Good to know I have the process licked for the next PoC coin Unfortunately I STILL don't have any BURST as I don't have any spare capacity at home so haven't been able to mine at all So if anyone would like to donate some coins to offset the cost of testing all of this, my address is BURST-WADY-CBZE-HSJU-2NH5G Many thanks! thanks for sharing. sent you some for your efforts. |
|
|
|
|
uray
|
|
August 15, 2014, 12:02:25 PM |
|
If anyone is interested, the conclusion of my test to see if I could speed up plot generation by farming it out using cluster/cloud computing is: Yes it can be done, but it is probably not worth it. This is what I did using Amazon EC2... First I created a single instance (2 core) to act as the server for the plot storage and also act as the wallet server / miner. This instance had a 1TB Elastic Block Store volume attached to it (1TB is max EBS volume size on AWS). I made this volume available to the network using NFS I then created a "plot generator" instance with much higher CPU capacity (C3.xlarge 8 core). I mounted the shared volume so it appeared like a local disk and started creating 10GB plots I then created a few scripts so that upon startup the instance would auto-mount the NFS volume, figure out what the last used nonce range was, and start mining from the next 10GB plot Finally, I created an image of this instance and spooled up 100 more instances like it (spot rates, nice and cheap). To begin with it all looked great but I soon hit the bandwidth limit of the instance I was using as the server. In essence the server didn't have enough network bandwidth to cope with all of the data being copied to it. This restricted plot creation to a little over 100GB / hour. Changing the instance type of the server instance to one with a "high" network performance got this up to around 400 GB/hour. If I had have left it running I would have created all 1 TB of plots in 2.5 hours, at a cost of around $20. This could have been repeated or even parallelized to create several 1TB volumes full of plots in a relatively short amount of time. After all the fiddling about getting it working, I spent around $70 testing this stuff out, only to conclude it was too much hassle. And as OP said earlier, the cost of EBS storage on AWS is too high to make this a viable long term mining option. That said, had I have done all of this on day one, I would have scaled the process out and had 10TB+ up within the first few hours and dominated the mining. Good to know I have the process licked for the next PoC coin Unfortunately I STILL don't have any BURST as I don't have any spare capacity at home so haven't been able to mine at all So if anyone would like to donate some coins to offset the cost of testing all of this, my address is BURST-WADY-CBZE-HSJU-2NH5G Many thanks! why u need NFS?, 1. first u create large instance 8 core or more 2. mount EBS to that instance 3. generate plot, while generating u r mining from it too (for 1 TB it will take about half day) 4. when plot generated, detach EBS, and shutdown + remove that instance 5. create new micro instance, attach that EBS and mining from it this will cost you about 60$ / TB / Month anyway, azure is cheaper, you can get it free, but i can't and won't tell you how |
|
|
|
|
|
SpeedDemon13
|
|
August 15, 2014, 12:02:52 PM |
|
If anyone is interested, the conclusion of my test to see if I could speed up plot generation by farming it out using cluster/cloud computing is: Yes it can be done, but it is probably not worth it. This is what I did using Amazon EC2... First I created a single instance (2 core) to act as the server for the plot storage and also act as the wallet server / miner. This instance had a 1TB Elastic Block Store volume attached to it (1TB is max EBS volume size on AWS). I made this volume available to the network using NFS I then created a "plot generator" instance with much higher CPU capacity (C3.xlarge 8 core). I mounted the shared volume so it appeared like a local disk and started creating 10GB plots I then created a few scripts so that upon startup the instance would auto-mount the NFS volume, figure out what the last used nonce range was, and start mining from the next 10GB plot Finally, I created an image of this instance and spooled up 100 more instances like it (spot rates, nice and cheap). To begin with it all looked great but I soon hit the bandwidth limit of the instance I was using as the server. In essence the server didn't have enough network bandwidth to cope with all of the data being copied to it. This restricted plot creation to a little over 100GB / hour. Changing the instance type of the server instance to one with a "high" network performance got this up to around 400 GB/hour. If I had have left it running I would have created all 1 TB of plots in 2.5 hours, at a cost of around $20. This could have been repeated or even parallelized to create several 1TB volumes full of plots in a relatively short amount of time. After all the fiddling about getting it working, I spent around $70 testing this stuff out, only to conclude it was too much hassle. And as OP said earlier, the cost of EBS storage on AWS is too high to make this a viable long term mining option. That said, had I have done all of this on day one, I would have scaled the process out and had 10TB+ up within the first few hours and dominated the mining. Good to know I have the process licked for the next PoC coin Unfortunately I STILL don't have any BURST as I don't have any spare capacity at home so haven't been able to mine at all So if anyone would like to donate some coins to offset the cost of testing all of this, my address is BURST-WADY-CBZE-HSJU-2NH5G Many thanks! thanks for sharing. sent you some for your efforts. Thanks also paul. I would send you some, but no luck for the pass 72 hours plus mining. These guys with smaller hdd's are getting block left and right with 48 hours.... |
CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911 |
|
|
|
|
|
ReDPoiSoN
|
|
August 15, 2014, 12:10:10 PM |
|
What is "Generate token" in the wallet home page!?
|
|
|
|
|
tricass
Sr. Member
Offline
Activity: 394
Merit: 250
Crypto enthusiast
|
|
August 15, 2014, 12:14:07 PM |
|
If anyone is interested, the conclusion of my test to see if I could speed up plot generation by farming it out using cluster/cloud computing is: Yes it can be done, but it is probably not worth it. This is what I did using Amazon EC2... First I created a single instance (2 core) to act as the server for the plot storage and also act as the wallet server / miner. This instance had a 1TB Elastic Block Store volume attached to it (1TB is max EBS volume size on AWS). I made this volume available to the network using NFS I then created a "plot generator" instance with much higher CPU capacity (C3.xlarge 8 core). I mounted the shared volume so it appeared like a local disk and started creating 10GB plots I then created a few scripts so that upon startup the instance would auto-mount the NFS volume, figure out what the last used nonce range was, and start mining from the next 10GB plot Finally, I created an image of this instance and spooled up 100 more instances like it (spot rates, nice and cheap). To begin with it all looked great but I soon hit the bandwidth limit of the instance I was using as the server. In essence the server didn't have enough network bandwidth to cope with all of the data being copied to it. This restricted plot creation to a little over 100GB / hour. Changing the instance type of the server instance to one with a "high" network performance got this up to around 400 GB/hour. If I had have left it running I would have created all 1 TB of plots in 2.5 hours, at a cost of around $20. This could have been repeated or even parallelized to create several 1TB volumes full of plots in a relatively short amount of time. After all the fiddling about getting it working, I spent around $70 testing this stuff out, only to conclude it was too much hassle. And as OP said earlier, the cost of EBS storage on AWS is too high to make this a viable long term mining option. That said, had I have done all of this on day one, I would have scaled the process out and had 10TB+ up within the first few hours and dominated the mining. Good to know I have the process licked for the next PoC coin Unfortunately I STILL don't have any BURST as I don't have any spare capacity at home so haven't been able to mine at all So if anyone would like to donate some coins to offset the cost of testing all of this, my address is BURST-WADY-CBZE-HSJU-2NH5G Many thanks! thanks for sharing. sent you some for your efforts. Thanks also paul. I would send you some, but no luck for the pass 72 hours plus mining. These guys with smaller hdd's are getting block left and right with 48 hours.... i guess that's the frustrating thing about this coin. it does seem like luck has a lot to do with it. it would be interesting to get a poll going to see what the average number of block found per miner is so far. |
|
|
|
|
SpeedDemon13
|
|
August 15, 2014, 12:22:46 PM
Last edit: August 15, 2014, 12:38:17 PM by SpeedDemon13 |
|
If anyone is interested, the conclusion of my test to see if I could speed up plot generation by farming it out using cluster/cloud computing is: Yes it can be done, but it is probably not worth it. This is what I did using Amazon EC2... First I created a single instance (2 core) to act as the server for the plot storage and also act as the wallet server / miner. This instance had a 1TB Elastic Block Store volume attached to it (1TB is max EBS volume size on AWS). I made this volume available to the network using NFS I then created a "plot generator" instance with much higher CPU capacity (C3.xlarge 8 core). I mounted the shared volume so it appeared like a local disk and started creating 10GB plots I then created a few scripts so that upon startup the instance would auto-mount the NFS volume, figure out what the last used nonce range was, and start mining from the next 10GB plot Finally, I created an image of this instance and spooled up 100 more instances like it (spot rates, nice and cheap). To begin with it all looked great but I soon hit the bandwidth limit of the instance I was using as the server. In essence the server didn't have enough network bandwidth to cope with all of the data being copied to it. This restricted plot creation to a little over 100GB / hour. Changing the instance type of the server instance to one with a "high" network performance got this up to around 400 GB/hour. If I had have left it running I would have created all 1 TB of plots in 2.5 hours, at a cost of around $20. This could have been repeated or even parallelized to create several 1TB volumes full of plots in a relatively short amount of time. After all the fiddling about getting it working, I spent around $70 testing this stuff out, only to conclude it was too much hassle. And as OP said earlier, the cost of EBS storage on AWS is too high to make this a viable long term mining option. That said, had I have done all of this on day one, I would have scaled the process out and had 10TB+ up within the first few hours and dominated the mining. Good to know I have the process licked for the next PoC coin Unfortunately I STILL don't have any BURST as I don't have any spare capacity at home so haven't been able to mine at all So if anyone would like to donate some coins to offset the cost of testing all of this, my address is BURST-WADY-CBZE-HSJU-2NH5G Many thanks! thanks for sharing. sent you some for your efforts. Thanks also paul. I would send you some, but no luck for the pass 72 hours plus mining. These guys with smaller hdd's are getting block left and right with 48 hours.... i guess that's the frustrating thing about this coin. it does seem like luck has a lot to do with it. it would be interesting to get a poll going to see what the average number of block found per miner is so far. It is, but you get use to it when it comes to solo mining crypto-currency. Seeing people with 30GB to 80 GB hdd's finding a block to 3 blocks within 48 hours is just surreal at times.... |
CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911 |
|
|
unsoindovo
Legendary
Offline
Activity: 1932
Merit: 1042
https://locktrip.com/?refId=40964
|
|
August 15, 2014, 12:40:24 PM |
|
hi all!! just to understand browser wallet http://localhost:8125/. i login into wallet browser with my passphrases.txt code. when i do "copy numeric account id" i correctly found the number generated with run_generate.bat and written inside address.txt. but i dont understand why my account ID "es.: BURST-XXXX-YYYY-ZZZZ" change every time i logoff wallet browser and i do a new login. This behaviour is correct? or i do something wrong? thanks!! |
|
|
|
|
paulthetafy
|
|
August 15, 2014, 12:43:35 PM |
|
If anyone is interested, the conclusion of my test to see if I could speed up plot generation by farming it out using cluster/cloud computing is: Yes it can be done, but it is probably not worth it. This is what I did using Amazon EC2... First I created a single instance (2 core) to act as the server for the plot storage and also act as the wallet server / miner. This instance had a 1TB Elastic Block Store volume attached to it (1TB is max EBS volume size on AWS). I made this volume available to the network using NFS I then created a "plot generator" instance with much higher CPU capacity (C3.xlarge 8 core). I mounted the shared volume so it appeared like a local disk and started creating 10GB plots I then created a few scripts so that upon startup the instance would auto-mount the NFS volume, figure out what the last used nonce range was, and start mining from the next 10GB plot Finally, I created an image of this instance and spooled up 100 more instances like it (spot rates, nice and cheap). To begin with it all looked great but I soon hit the bandwidth limit of the instance I was using as the server. In essence the server didn't have enough network bandwidth to cope with all of the data being copied to it. This restricted plot creation to a little over 100GB / hour. Changing the instance type of the server instance to one with a "high" network performance got this up to around 400 GB/hour. If I had have left it running I would have created all 1 TB of plots in 2.5 hours, at a cost of around $20. This could have been repeated or even parallelized to create several 1TB volumes full of plots in a relatively short amount of time. After all the fiddling about getting it working, I spent around $70 testing this stuff out, only to conclude it was too much hassle. And as OP said earlier, the cost of EBS storage on AWS is too high to make this a viable long term mining option. That said, had I have done all of this on day one, I would have scaled the process out and had 10TB+ up within the first few hours and dominated the mining. Good to know I have the process licked for the next PoC coin Unfortunately I STILL don't have any BURST as I don't have any spare capacity at home so haven't been able to mine at all So if anyone would like to donate some coins to offset the cost of testing all of this, my address is BURST-WADY-CBZE-HSJU-2NH5G Many thanks! At $70 per day, that's $2100 per month. You can nearly buy a mobo, a used 6/12 core (12/24 threads) Intel cpu, Ram and some HDD's for that price, give or take....LOL Sorry you misunderstood - I spent $70 figuring this out. It would cost $20 to generate 1 TB in 2.5 hours (instead of a couple of days so you are mining at full pelt quicker). Once it is generated, it would cost around $15 a month for the server and $100 a month for storage. And at current rates that would probably still be profitable |
|
|
|
|
|
luxe
|
|
August 15, 2014, 12:44:07 PM |
|
hi all!! just to understand browser wallet http://localhost:8125/. i login into wallet browser with my passphrases.txt code. when i do "copy numeric account id" i correctly found the number generated with run_generate.bat and written inside address.txt. but i dont understand why my account ID "es.: BURST-XXXX-YYYY-ZZZZ" change every time i logoff wallet browser and i do a new login. This behaviour is correct? or i do something wrong? thanks!! passphrases is your login ... you can not change it without getting a new address ... they are bound to each other! |
|
|
|
|
|
cad_cdn
|
|
August 15, 2014, 12:46:29 PM |
|
so, to continue.... 1.3Tb over 3 seperate pc's, for 2 days, found 1 block on the last machine I added with the smallest -lot of 50Gb.
|
|
|
|
|
|
paulthetafy
|
|
August 15, 2014, 12:46:55 PM |
|
If anyone is interested, the conclusion of my test to see if I could speed up plot generation by farming it out using cluster/cloud computing is: Yes it can be done, but it is probably not worth it. This is what I did using Amazon EC2... First I created a single instance (2 core) to act as the server for the plot storage and also act as the wallet server / miner. This instance had a 1TB Elastic Block Store volume attached to it (1TB is max EBS volume size on AWS). I made this volume available to the network using NFS I then created a "plot generator" instance with much higher CPU capacity (C3.xlarge 8 core). I mounted the shared volume so it appeared like a local disk and started creating 10GB plots I then created a few scripts so that upon startup the instance would auto-mount the NFS volume, figure out what the last used nonce range was, and start mining from the next 10GB plot Finally, I created an image of this instance and spooled up 100 more instances like it (spot rates, nice and cheap). To begin with it all looked great but I soon hit the bandwidth limit of the instance I was using as the server. In essence the server didn't have enough network bandwidth to cope with all of the data being copied to it. This restricted plot creation to a little over 100GB / hour. Changing the instance type of the server instance to one with a "high" network performance got this up to around 400 GB/hour. If I had have left it running I would have created all 1 TB of plots in 2.5 hours, at a cost of around $20. This could have been repeated or even parallelized to create several 1TB volumes full of plots in a relatively short amount of time. After all the fiddling about getting it working, I spent around $70 testing this stuff out, only to conclude it was too much hassle. And as OP said earlier, the cost of EBS storage on AWS is too high to make this a viable long term mining option. That said, had I have done all of this on day one, I would have scaled the process out and had 10TB+ up within the first few hours and dominated the mining. Good to know I have the process licked for the next PoC coin Unfortunately I STILL don't have any BURST as I don't have any spare capacity at home so haven't been able to mine at all So if anyone would like to donate some coins to offset the cost of testing all of this, my address is BURST-WADY-CBZE-HSJU-2NH5G Many thanks! why u need NFS?, 1. first u create large instance 8 core or more 2. mount EBS to that instance 3. generate plot, while generating u r mining from it too (for 1 TB it will take about half day) 4. when plot generated, detach EBS, and shutdown + remove that instance 5. create new micro instance, attach that EBS and mining from it this will cost you about 60$ / TB / Month anyway, azure is cheaper, you can get it free, but i can't and won't tell you how NFS was to allow 100x8 core machines to generate plots on it simultaneously, speeding up the time to generate the plots significantly (the point of the test!). Yes you could use a micro instance once done, but EBS still costs $100 per TB per month. Also with a single 8 core generating 1TB plots would still take 2 days by my calculation. The point was that if difficulty is increasing massively in that time, you would be better off spending $20 or whatever up front to parallelize the plot creation so you are mining with large plots sooner. |
|
|
|
|
|
paulthetafy
|
|
August 15, 2014, 12:47:41 PM |
|
thanks for sharing. sent you some for your efforts.
Many thanks! |
|
|
|
|
|
HunterS
|
|
August 15, 2014, 12:48:05 PM |
|
i have mined since start.finally finsished plotting 1.8 TB hard drive today and i have found 32 blocks
|
|
|
|
kcanup
Legendary
Offline
Activity: 1484
Merit: 1000
|
|
August 15, 2014, 12:49:42 PM |
|
Unfortunately I STILL don't have any BURST as I don't have any spare capacity at home so haven't been able to mine at all So if anyone would like to donate some coins to offset the cost of testing all of this, my address is BURST-WADY-CBZE-HSJU-2NH5G Many thanks! Sent you some Burst buddy.. Thanks for trying to help burst community |
|
|
|
|
kcanup
Legendary
Offline
Activity: 1484
Merit: 1000
|
|
August 15, 2014, 12:50:04 PM |
|
i have mined since start.finally finsished plotting 1.8 TB hard drive today and i have found 32 blocks
Wow  |
|
|
|
|
unsoindovo
Legendary
Offline
Activity: 1932
Merit: 1042
https://locktrip.com/?refId=40964
|
|
August 15, 2014, 12:54:16 PM |
|
how to increment plot generation speed?
adding CPU/RAM/SSD?
|
|
|
|
|
cad_cdn
|
|
August 15, 2014, 12:55:17 PM |
|
i have mined since start.finally finsished plotting 1.8 TB hard drive today and i have found 32 blocks
can someone please advise on these plots settings on my primary pc: 1097082171119035817_0_204800_1000 1097082171119035817_1_800000_500 1097082171119035817_1_3200000_500 (still plotting after 2+ days) 1097082171119035817_1_80000000_500 (still plotting after 2+ days) thinking I error'd in these plot settings, maybe I need to redo...? |
|
|
|
|
|
HunterS
|
|
August 15, 2014, 12:55:42 PM |
|
how to increment plot generation speed?
adding CPU/RAM/SSD?
not sure how to make it quicker but i was creating 2 plots at once on my hdd |
|
|
|
|
