@SRBOOTH:

Also, a quick look at the AEON appdata folder will tell you if pruning executed correctly at least once (and saved).
You should find that blockchain.bin is about 2.8GB, while blockchain-pruned.bin is about 1.66GB.

@SRBOOTH:

There's no external GPU solo miners for any cryptonote as far as I know. Most definitely not for nvidia, since ccminer will only work with pools. If you really want to solo mine with nvidias (or AMDs AFAIK), you'll need to setup a private pool. That should be an interesting/fun project btw.   Happy Mining!

Edit: on the pruned version compiled for windows, I've posted (unofficial) binaries just yesterday:
https://bitcointalk.org/index.php?topic=641696.msg12285871#msg12285871

Official ones should not take long I suppose, since Arux is back from all his summer partying  

Edit ^2: the light-node (pruned) working well for me so far. I have made a couple of transfers without any issues, I have solo mined a block, and have gone through the cycle seeing a misbehaving peer get blocked. Good stuff!   

Thanks GingerAle,
That is exactly the performance range I would expect, like Smooth was saying, roughly double the performance of regular cryptonight. You can definitely get it to run faster with overclocking, as cryptonight & cryptonight-light are more tolerant to overclocking than most other algorithms. Anyhow, looking really good, cheers!

Also a +1 about drivers, some versions are faster, others are slower. Even across different systems, it's not always the same driver that performs best (cards on risers vs cards directly on slots, paired with fast CPU vs paired with slow CPU, etc).

Correct smooth. But what I've seen in my limited experience here (as I don't have the ideal GPU models), is that without specific tuning for cryptonight-light, the performance will not automagically double, using the same launch settings as for regular cryptonight. I had observed ccminer hashing just marginally faster, if selecting cryptonight-light vs cryptonight on the same baseline settings (at least on Windows).

With proper launch settings, yes, the performance should be roughly double that of regular cryptonight. With ccminer, the ideal cryptonight-light performance, is probably found by using a launch string that uses double the number of threads as for regular cryptonight - in order to take advantage of the smaller workload.
As I understand, the ccminer thread synchronization and memory access behaves very differently in Linux, causing Linux miners to see most of the cryptonight-light gains even without tuning their launch parameters. In any case, proper tuning will provide the best results.

Thank you both for the inputs.

I would bet on something specific to that Windows setup as fault for the low speed, if not the dreaded "operator error"  since that Windows hashrate sounds about right for regular cryptonight (as in missing the -A switch). Linux does generally better on the same hardware, that's for sure, and more so with any algorithm that is memory hard, where the Windows (WDDM) driver overhead really bogs down the performance.

Well, could also be that your Windows launch settings (threads & blocks) were not optimal. While on Linux, sub-optimal launch settings go partly unnoticed due to the comparative hashrate boost from Linux vs Windows. On Windows, less-than-perfect settings will cause much more of a performance hit.

I don't have the proper launch settings for the 750TI myself though, don't have those cards anymore. I do have reports of cryptonight-light performance in the region of 500 h/s on these cards, even on Windows. Note that both cryptonight & cryptonight-light allow for massive overclocks on the 750 TI, seeing as the GPU is hardly stressed at all.

Here are freshly compiled (and unofficial) AEON light-node binaries for testing on Windows:
I built these on Win-10, Boost 1.59, VStudio 2015, and look to be working fine on my Win-8 box as well.
Aeon-Win-x64-light-node-beta

Instructions starting up a light-node are here:
Pruning (aka Light Full Node) test release

And the FAQ on pruning just upthread:
Pruning FAQ

So for now, I'll be running a light-node instead of the archive one, and solo mining on the daemon as before. I'll most likely run a full node in the long term as I have the resources available, but anyhow I figured that testing light-node is more useful right now.

@SRBOOTH: thanks for the feedback 

Cheers!

Thanks for the feedback jwinterm. I know that most up-to-date ccminer forks are built with static libraries (so separate dll's are not required), but the cryptonight base from which cryptonight-lite was made, was a much older fork and generally not maintained, so I doubt it was configured in such fancy ways (not that I know enough to really make a call either way).
This helps though, as missing (or conflicting) dll's might also be causing the issue for SRBOOTH.

The issue for SRBOOTH was outdated drivers, just confirmed over PM and so all is well for him now  
I'm not sure now, but I think I had built with cuda 7.5, which would explain why a recent driver is required. Hmm... maybe I mentioned something around the time? Old farts have crappy memory  
 
For anyone interested in trying out my most up-to-date build, here's one with some personal tweaks and both cuda 6.5 & 7.5 flavors. I cannot for the life of me recall what compute levels I had included on this build, but at minimum, it should be compute 5.0 and upwards. Might also do better at regular cryptonight mining, for whatever that's worth...
ccminer-cryptonight-lite-beta-3

Edited to add: Note that most up-to-date build and personal tweaks don't necessarily make it any faster!    This version might do better on some cards, worse on others (for all I know, might do worse on all of them, unfortunately I cannot afford the testing time right now to go back and compare, all of my GPUs are tied up).

And here's a bunch of dll's, should have everything that might possibly be necessary to run any current x86 ccminer (not x64), as well as it most definitely has some extra (needless) stuff in there... It's my go to copy/paste set from many ccminer adventures over time  
ccminer-dll-pack

I'm exchanging PMs with SRBOOTH to see if we can figure out why the ccminer binaries that I posted are not working for him.
@jwinterm, if I read correctly, you also had some trouble on Windows. In case you used the binaries that I had posted, do you recall what was the error on your end?

@smooth, awesome job on the pruning release! I've been happy solo mining, hitting at least one block per day, sometimes two. Need all the power we can have against nefarious Moooooooooo.    I'll see if I can build the pruning release and start testing that as well tonight.

@smooth, fwiw, I concur with your reasoning on how to address this wallet refresh issue and pruning strategy. Good stuff! 

@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! 

What you just described is one unique characteristic in GSY, which is the Confront feature.

There are other unique aspects to the platform, as well as other monetization opportunities.
One I find most interesting, is that this project is also a crowdfunding for an actual game to be developed. Once completed, this particular game, can drive any sort of revenue workflow that the developers might desire, with the obvious possibility of rewarding both the GSY team, as well as players/holders.

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.

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. 

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

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://bitcointalk.org/index.php?topic=641696.msg11946271#msg11946271

Cheers!

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

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:

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!
 

Super. Thanks again! 

Thanks for clearing it up mprep.
I'm still unclear about the swearing though. Is that acceptable?

I'm not asking permission to go on a cursing rampage btw     I think this particular post that was deleted was in fact my worst ever use of language around here  

EDIT: And I'll have the apple sauce, thank you 

Hi there!

I've had a post deleted by a forum moderator, and while I suspect the reason for the removal, I would appreciate a clarification from any forum moderator as to the rule in question. My point is not to troll the moderators or the forum, I just want to be certain of what caused by post to be deleted, so that I can stick to the rules and avoid future posts from taking the same fate.

Here's the message and deleted post:


The bottom portion of the post was quite on-topic, and had significant followup from both the thread OP as well as other community members.

The top portion was a brief reaction to a post by one persistent troll that keeps posting on that thread with all sorts of non-sense propaganda, trying to push a certain agenda forward. This is a fancy troll, in that he writes eloquently enough that he might persuade the less critical readers, using systematic deception tactics and extreme persistence.
For this reason alone, I granted him a response. Otherwise he remains on my ignore list and I don't generally respond to trolls.

So my question is: was my post deleted due to swearing (couple instances of the F word), or was it something else? Is swearing strictly - or even casually - against the forum rules? I've read a good few newbie guides and such, but haven't really found this to be stated anywhere...

Thanks for your time.

I had registered previously, have been able to login just now, and browsed the games list. I'm unable to test drive actual game launch right now as I'm over a remote session, but will report back once I've had a chance to run some games. Good Job! 

Thanks for clearing it up fluffypony. I should also correct my previous statement: The wallet rescan was not as impressively fast as the full blockchain sync, but it was not really slow either. I just later realized that I had already initiated solo mining on the daemon, so my CPU was having to work pretty hard