Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - pvp1982

#1
Quote from: Brekyrself on January 16, 2014, 08:02:40 PM
CPU: Intel Xeon L5639 @ 3.52ghz
RAM: 12 GB DDR3 RAM @ 1760mhz
OS: Windows Vista (64bit)
Software: yam-yvg1900-M7j-win64-Nehalem
Threads:11
PTS Agg. CPM (512 MB): 355 (AV=21 after AV-optimization)

Can get more CPM with more threads however it starts to slow down gpu mining on the same machine.

wow, how is your L5639 running at 3.52 Ghz?

#2
Great post by jh00
#3
anyone tried this miner?

64 bit version?
#4
windows 7 64bit binary?
#5
Quote from: BitThink on December 26, 2013, 01:32:00 PM
Why the reject rate is so high?

same here... tons of rejects.

#6
Quote from: vorksholk on December 26, 2013, 06:18:19 AM
Quote from: marlowbg on December 26, 2013, 06:16:05 AM
Why threads 12 is invalid? There are many cpus out there with 12 cores, please fix this...

For now, just run one instance with 8 and one with 4.

this is what I also plan to do :) I hope a fix will come as well.
#7
Why threads 12 is invalid? There are many cpus out there with 12 cores, please fix this...
#8
hash generated - 2805 / 1968 / 2228977017
submit: 036d3929486b4ba07dbc68f6a172a5456216c3b82cc5e87d83a589d68c8e8113
hash generated - 13053 / 1968 / 3171305550


I think there is still some pools issue - with Submits,

the response from the server is missing after "submit" message

EDIT: down again

system:111
connecting to 162.243.216.74:1339
system:111
connecting to 162.243.216.74:1339
#9
what is the OS (linux flavour) used?
#10
Quote from: KillerByte on December 25, 2013, 08:36:04 PM
dmesg -T | tail

[Wed Dec 25 20:17:24 2013] systemd-journald[101]: Failed to write entry (25 items, 211571354 bytes) despite vacuuming, ignoring: Argument list too long
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Deleted empty journal /var/log/journal/bb9d0a52a41243829ecd729b40ac0bce/user-1000@c4ef46c298b543f9ab9fbe27625479c4-0000000000000000-0000000000000000.journal (3735552 bytes).
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Vacuuming done, freed 3735552 bytes
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Failed to write entry (25 items, 237032090 bytes) despite vacuuming, ignoring: Argument list too long

... and that message is repeated many times.


Hmm I don't think it's related to the software buffer overflow error.
#11
what is there in kernel log?

dmesg -T | tail

or only

dmesg

?
#12
Quote from: KillerByte on December 25, 2013, 08:29:31 PM
any ideas on the buffer overflow message?

Quote*** buffer overflow detected ***: memorypool terminated

some attack directed to the port on which the pool is running?

#13
Quote

EDIT: 1000+ clients connecting. That is probobly part of why. I have the debugger running. ready for another error.

Good problem to have actually :)
#14
system:111
hash generated - 10273 / 1968 / 992674184
connecting to 162.243.216.74:1339
system:111
hash generated - 988 / 1968 / 732418756

this is what happens with my node
#15
Quote from: svyatoslav on December 25, 2013, 07:25:36 PM
stats for 64 core and 64 threads

[STATS] 2013-12-25 19:23:21 | SHARES: 5 (100.0% | 5.4/h), VL: 5 (62.5%), RJ: 3 (37.5%), ST: 0 (0.0%)

I think you have to keep it running for some time to get proper stats, because there is some luck involved also... as far as I know.

Otherwise REJECTS are not good to have... it happens to me also.