Topic: [HYP] HyperStake | Generous Reward Staking | Advanced Staking Controls & Wallet - page 154. (Read 679332 times)

CPU problems officially solved Update to the latest repo for less CPU consumption. This was really only affecting clients that had no mintable coins.

Commit: https://github.com/hyperstake/HyperStake/commit/84b4374f4f9c93197e8791cd071675beba713e04

Understandable. But it is nice to get your opinion on daemons and code occasionally   Where will I be able to find this open source repo?

The IPv6 is probably just between the computer and the individual's router.

I am not quite sure about why some coin daemons spike in CPU usage or become memory hogs. A while back I needed to implement a policy of not getting involved in patching and/or coin development with the coins on CCE, it would seriously cut down on the time I had for CCE development. I found it easier to code CCE around the daemon quirks and in order to keep the CCE code uniform, I implement these quirks as configuration options. There was one exception, but only because there was no way to code around it.

I know it appears the CCE 4 is taking a long time in development, but I want to make sure that everything is running as good as possible and future improvements will not involve the amount of rewriting I am doing from 3.5 to 4.0. It took two months to decide the final structure of the database loader for 4.0, and the database loader is only half the equation, the web server is what is being worked on now.

I have decided to release a base version of the  database loader for 4.0 as open source.I have been taking time with the database loader (and its associated modules) to make it open source friendly.
This will most likely be released at the same time CCE 4 is deployed to take advantage of the PR opportunity.

There are so many options being added to CCE 4 that most likely it will be offered in a tiered format. From very basic free explorers (more basic then CCE 3.5) with advertisement type funding to a top tier with things like blockchain downloads updated weekly, coin client downloads, user accounts, advanced API features for statistics and "lite" clients , user and developer explorer customizations, coin website hosting and much more.

Once a larger chunk of the new features is finalized, I will  post them in the CCE thread.

The point is, CCE 4 is going to be a different beast from CCE 3.5. It is turning out to be a complete rewrite, and I believe in the end it will be worth the wait.

hooray! im not completely crazy! i'll have to work that more...

That was my first guess (but this isn't actually activated by default), my second guess was the code to request blocks from peers more frequently - but after disabling this code I see no impact. I am actually thinking that it might be the liteStake code is only being picked up by daemons with mature coins. I'll do some fiddling around with the code to confirm my suspicion.

https://bitcointalksearch.org/topic/m.10475658

This one??

didnt you fix something in between 1.1.0 and 1.1.2 that effected cpu usage?

(going through the commits and for the life of me I can't find it... maybe I imagined that)

Good news on the DB Excited to see progress being made.

Hmmm. What is confusing me is that certain daemons are running fairly light.

It is not unusual for Hyperstake to be heavy on the CPU resources on CCE.



In the image there are two Hyperstaked threads running over 100% of a cpu core.

Hyperstake is not the only coin daemon that does this.

On a related note:

The new database loader has been patched into all the explorers and restart tests were preformed over the last couple of days.

google and found pidof command; killed daemon, restarted pi and getinfo is shwing is sync from block 0

dont know what happend i guess i need to learn linux thanks for the help btw what command is for check debug log files

You can always check your debug.log too. If it is syncing you should see things like this in it, and it will tell you how far along it is:

ok i ll wait a day more than

It is probably syncing. It can take a while before RPC commands are available.

guys i m writing again to get help

i have to reinstalled daemon in another Raspberry pi, its been 48hrs i started ./hyperstaked but whenever i do getinfo i am getting error couldnt connect to the server. raspberry pi CPU usage is showing 100% which means background something is going but dont know what exactly happening. my config file is

need help

Has anyone noticed their daemon running quite heavy? I have a few taking 99% cpu load. Wondering if we have someone trolling the network or maybe if it is a problem with the code. I will be doing some more testing, please let me know if you are seeing anything like this.

It appears like that if you are using IPv6, wonder how it would affect addnodes??

My IP switches to an IPV6 IP

Hmmm thats odd :/

My ip is different too. Mine is 370H55V.