Other > DevShares

Attack on DevShares / client misbehaving?

(1/4) > >>

wackou:
looks like the misbehaving client has left the network at 00:00 UTC last night (times on the plot are UTC+1):

wackou:
ok, thanks. Will report again when the new devshares is out, then. OTOH bitshares 0.7.0 is running very smoothly and the memory leak is gone, great job!

vikram:
It's very strange and we don't really know what's going on. We are working to get DVS 0.8 out as soon as we can which has lots of changes; if the behavior still persists with the latest code then we will have to investigate more closely.

wackou:
an update on the situation:

last night the cpu usage on the spike has been slowly fading out:



however, today it starting going up a lot more again, and nearly maxes out 1 core now:



(it doesn't show anything before ~15:20 because I was running it on another machine at that time)

Maybe it is related to the current fork with the init delegates somehow?

wackou:
my devshares delegate (first screenshot of this thread, this post: https://bitsharestalk.org/index.php?topic=14852.msg192315#msg192315) is running 0.6.3 on debian jessie, 2-core xeon and 4G RAM.

the second and third screenshot are from my laptop which is a 2012 macbook pro, with osx 10.9, devshares 0.6.3 as well.

here's a new one from my laptop where I completely removed the devshares dir:



as you can see, it starts by synchronizing the blockchain and then the same pattern appears. Note that total average cpu usage is not really that high, it's more the pattern that bothers me (so for instance just checking your average daily usage of your server will not show any unusual cpu usage). I am pretty sure also that this appeared 3 days ago and wasn't present before.

Unrelated to this issue, but still worth noticing, is that my BitShares delegate has an extremely low cpu usage (uncannily low, actually), at the cost of a small memory leak (this appeared in bts 0.6.2, 0.6.1 had a more normal cpu usage and no mem leak). Here's a screenshot (specs are the same as my dvs delegate, 2-core xeon and 4G RAM)

Navigation

[0] Message Index

[#] Next page