[ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 226.

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: myagui on August 24, 2015, 03:16:47 PM

@smooth,

As I had compiled from git just yesterday, I am also running a pruned node, right? Just wondering.
All is working well here, just found a block solo, yay!

No pruning is not in git yet, and the first version with pruning (very soon) will be a designated test version, not a release.

The current official release does have some memory and storage optimizations I came across when working on pruning that are in there.

Quote

just found a block solo

Nice!

Thank you for supporting the network!

myagui

legendary

Activity: 1154

Merit: 1001

@smooth,

As I had compiled from git just yesterday, I am also running a pruned node, right? Just wondering.
All is working well here, just found a block solo, yay!

nikos64

sr. member

Activity: 283

Merit: 250

Quote from: myagui on August 24, 2015, 11:06:22 AM

Quote from: nikos64 on August 24, 2015, 08:32:51 AM

Quote from: myagui on August 23, 2015, 07:26:35 PM

Cheers Smooth! It's an i7-4770, standard clocks and all, running 6 threads, above normal priority.

Why don't you run all threads/cores but in low priority? Windows can manage just fine the other jobs that way, and you can have the max hashrate too.
I even play Left 4 Dead 2 without stop mining. The hashrate drops from 850 h/s to 550 while playing but that's all, I have to do nothing else.

These days, that box is primarily a GPU mining rig, and the current GPU work is actually very sensitive to any moderate CPU usage. Optimal performance (giving priority to current GPU work), was found by setting affinity to have 2 dedicated threads for the GPU miner. I can then do whatever on the other 6 threads, that the GPUs remain at full performance.

I see... I do the same thing when I have something to mine with my GPU. Not much GPU mining lately though.

myagui

legendary

Activity: 1154

Merit: 1001

Quote from: nikos64 on August 24, 2015, 08:32:51 AM

Quote from: myagui on August 23, 2015, 07:26:35 PM

Cheers Smooth! It's an i7-4770, standard clocks and all, running 6 threads, above normal priority.

Why don't you run all threads/cores but in low priority? Windows can manage just fine the other jobs that way, and you can have the max hashrate too.
I even play Left 4 Dead 2 without stop mining. The hashrate drops from 850 h/s to 550 while playing but that's all, I have to do nothing else.

These days, that box is primarily a GPU mining rig, and the current GPU work is actually very sensitive to any moderate CPU usage. Optimal performance (giving priority to current GPU work), was found by setting affinity to have 2 dedicated threads for the GPU miner. I can then do whatever on the other 6 threads, that the GPUs remain at full performance.

bangomatic

legendary

Activity: 1246

Merit: 1000

ARK Team likes to ban and delete posts in reddit.

Quote from: smooth on August 24, 2015, 10:09:25 AM

Pruning update

I'm running two pruned nodes right now, as a bit of a final performance test, after completing several functional tests.

Assuming no problem arise I will be dropping a test release within several hours.

Great update! Thanx!

smooth

legendary

Activity: 2968

Merit: 1198

Pruning update

I'm running two pruned nodes right now, as a bit of a final performance test, after completing several functional tests.

Assuming no problem arise I will be dropping a test release within several hours.

nikos64

sr. member

Activity: 283

Merit: 250

Quote from: myagui on August 23, 2015, 07:26:35 PM

Cheers Smooth! It's an i7-4770, standard clocks and all, running 6 threads, above normal priority.

Why don't you run all threads/cores but in low priority? Windows can manage just fine the other jobs that way, and you can have the max hashrate too.
I even play Left 4 Dead 2 without stop mining. The hashrate drops from 850 h/s to 550 while playing but that's all, I have to do nothing else.

Phantas

sr. member

Activity: 311

Merit: 250

Quote from: MoneroMooo on August 24, 2015, 02:02:05 AM

Quote from: Phantas on August 24, 2015, 12:58:41 AM

http://aeonpool.mooo.com/ is down Sad

Back up now. Sorry about that, my ISP hiccuped and the dynamic DNS update did not trigger automatically this time.

no problem, thank you Wink

MoneroMooo

legendary

Activity: 1276

Merit: 1001

Quote from: Phantas on August 24, 2015, 12:58:41 AM

http://aeonpool.mooo.com/ is down Sad

Back up now. Sorry about that, my ISP hiccuped and the dynamic DNS update did not trigger automatically this time.

Radouch

newbie

Activity: 30

Merit: 0

Quote from: myagui on August 23, 2015, 06:37:31 PM

Thanks for the input Radouch. I'm not going to run a binary from a recent member as I don't have an isolated environment for testing right now, but perhaps that helps others.

I really appreciate your reaction, Myagui. No reaction makes me really uncertain if my reports are of any use.

Concerning binaries: better safe than sorry, no problem. I only want to stress that my account is one year old (and only 6 months younger than yours). I just prefer reading over writing, especially if I do not have anything meaningful to say.

Have a nice day :-)

Phantas

sr. member

Activity: 311

Merit: 250

http://aeonpool.mooo.com/ is down Sad

myagui

legendary

Activity: 1154

Merit: 1001

Cheers Smooth! It's an i7-4770, standard clocks and all, running 6 threads, above normal priority.

Frustrated with my earlier trouble with compiling on the original Windows box, I had a few more cracks at it, and finally sorted what the issue with compiling on that one as well. Suspecting that I had a broken boost setup, I rebuilt boost, then recompiled there, and presto, also got me working binaries. Happy camper. Cool

I'm not sure this needs correcting on the compilation instructions, could be my misunderstanding, but anyhow, that's how it worked for me - definitely the case on building boost 1.59 - not sure if it makes any difference on earlier versions, as the documented 1.57.

Where it reads:
b2 --toolset=msvc variant=release link=static threading=multi runtime-link=static address-model=64

I used instead:
b2 toolset=msvc variant=release link=static threading=multi runtime-link=static address-model=64

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: myagui on August 23, 2015, 06:37:31 PM

I see my hashrate restored while solo mining on the daemon (about 640h/s now), so thank you, looks that the issue is fixed!

Great!

That's a pretty nice hash rate! What CPU is that?

Quote

Side note, please update the OP with the revised compilation instructions as per the following post:
https://bitcointalksearch.org/topic/m.11946271

Cheers!

Done. Thanks for pointing out the update.

myagui

legendary

Activity: 1154

Merit: 1001

Thanks for the input Radouch. I'm not going to run a binary from a recent member as I don't have an isolated environment for testing right now, but perhaps that helps others.

I didn't manage to fix whatever issue is causing me grief with my regular Windows box, but I was able to compile the binaries on a freshly installed Win 10 VM. The binaries created on the Win 10 VM did work fine on my usual PC (Win 8.0).

For anyone else that might want to test these, do understand that I'm a relative newbie at compilation (most of my experience is with cudaminer/ccminer), so I doubt I'd be able to fix any issues one might find. The following link has binaries from the current code on git, and were compiled using a clean/fresh Windows 10 x64 VM with VStudio 2015 and Boost 1.59.
Aeon-Win-x64-0.9.2.0-git.zip

@smooth:
I see my hashrate restored while solo mining on the daemon (about 640h/s now), so thank you, looks that the issue is fixed!
Side note, please update the OP with the revised compilation instructions as per the following post:
https://bitcointalksearch.org/topic/m.11946271

Cheers!

Radouch

newbie

Activity: 30

Merit: 0

This morning version:

https://drive.google.com/file/d/0B7aFZCwh53eNd1F6LUJ5a3JlNTg/view?usp=sharing

Radouch

newbie

Activity: 30

Merit: 0

Quote from: myagui on August 22, 2015, 04:50:01 PM

Quote from: VladimirN on August 22, 2015, 04:38:14 PM

Quote from: Schild_ on August 22, 2015, 03:45:39 PM

Super quiet here... Grin

holidays... Roll Eyes

I used latest cmake (3.3), boost 1.57 and VStudio 2013 as described on the OP, and I'm on Win 8.0 x64.

I used boost 1.59 and VStudio 2015 and my compiled binaries run on Win 7 x64 without problems.
Only I had to rename some folder, but unfortunatelly do not remember which one...

myagui

legendary

Activity: 1154

Merit: 1001

Quote from: VladimirN on August 22, 2015, 04:38:14 PM

Quote from: Schild_ on August 22, 2015, 03:45:39 PM

Super quiet here... Grin

holidays... Roll Eyes

While on semi-holidays, I'm quietly acquiring a moderately larger position Wink

I'm really looking forward to test the newer version, largely to allow me the contribution of a solo mining daemon/node.
Will try to compile using the OP instructions tonight.

Edit: No luck at my 1st quick attempt at compiling. I eventually got binaries built, but there's some fatal error right at daemon start and it does not run at all. I'm pretty sure this is some issue with my build environment. I'll look into error messages and further troubleshooting when I get a break.

Edit #2: Just in case someone can easily point me in the right direction, here's the error I have when launching the daemon self-compiled:

Code:

2015-Aug-23 12:15:25.431831 aeon v0.9.2.0(@VERSION@)
2015-Aug-23 12:15:25.432832 Module folder: C:\Users\-removed-\aeon\build\src\Release\aeond.exe
2015-Aug-23 12:15:25.435836 Initializing p2p server...
2015-Aug-23 12:15:25.437837 ERROR c:\users\-removed-\aeon\src\p2p\net_node.inl:110 Exception at [node_server::init_config], what=unsupported version
2015-Aug-23 12:15:25.440839 ERROR c:\users\-removed-\aeon\src\p2p\net_node.inl:273 Failed to init config.
2015-Aug-23 12:15:25.442841 ERROR C:\Users\-removed-\aeon\src\daemon\daemon.cpp:174 Failed to initialize p2p server.
2015-Aug-23 12:15:25.445844 Mining has been stopped, 0 finished

I used latest cmake (3.3), boost 1.57 and VStudio 2013 as described on the OP, and I'm on Win 8.0 x64.
I think I saw some error concerning a "version.h" file when generating the configuration files or when compiling, not sure now and I have cleared the logs already. Will check it out again later.

Cheers!

VladimirN

sr. member

Activity: 405

Merit: 251

Quote from: Schild_ on August 22, 2015, 03:45:39 PM

Super quiet here... Grin

holidays... Roll Eyes

Radouch

newbie

Activity: 30

Merit: 0

Quote from: smooth on August 19, 2015, 03:23:05 AM

I think I located the problem with the Windows build. If someone wants to create a new binary from github HEAD, we can see if it fixed it.

Tonight I somehow managed to compile from GitHub for Windows (not much easy for me, who never ever compiled anything on Windows... :-) ). With 0.9.1.1 binaries I have got hash rate about 80 H/s, with 0.9.2.0 binaries I've got up to 160 H/s.

So, good work, Smooth! :-)

If you believe me, you can download my binaries from cryptoradouch . tk /aeon/aeon0.9.2.win64.zip
(sorry, but bitcointalk believes this is a suspicious link - this is my VPS...)

EDIT:
Now binaries of aeon 0.9.2.0 for Win 64 compiled by me are available on Google Drive, maybe Bitcointalk will like it more:
https://drive.google.com/file/d/0B7aFZCwh53eNLWtuOTVITF9jcDg/view?usp=sharing

Schild_

sr. member

Activity: 406

Merit: 250

Quote from: smooth on August 22, 2015, 03:46:19 PM

Quote from: Schild_ on August 22, 2015, 03:45:39 PM

Any news?

I am doing testing on pruning right now.

Hehe. Multitasking Smooth

Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 226. (Read 625666 times)