Show Posts
|
Pages: « 1 2 3 [4] 5 6 »
|
Test Excavator_v1.4.1a_NVIDIA_Win64_CUDA_9.1 Hardware Spec & setting:
GPU 0: Gigabyte Windforce 2 NVIDIA GeForce GTX 1060 3GB (Samsung) dedicate to mining GPU 1: Gigabyte NVIDIA GeForce GTX 650 2GB only for own use, not for mining OS: Windows 7 Service Pack 1 Video Driver: 390.65 MSI Afterburn: 4.4.2 Power limit: 72 => ~86 W Temp limit: 80 Core Clock: +168 Memmory Clock: +650
A. Neoscrypt - stell need much better tune till hit 700-720 kh/s aka see: - Excavator 1.4.1.a / 9.1 = 628.654 kH/s - Excavator 1.4.1.a = 614.909 kH/s - 628.654 (with 9.1) - 614.909 (with out 9.1) = 13.745 kH/s - Ccminer KlausT 8.19 -i 16 = 700 kH/s - Hsrminer - 710 > 720 kH/s - test run start on 2018-01-24 13:50:00 noo issue soo far beside speed & Web Api report see below
Question what is value or setting for json to set Excavator to run on equivalent of intensity of 16 - 18 ?
Web api report strange value 1.4.1.a with 9.1 & with out 9.1 - GPU Utilization 99%-100% when it suppose to be 100% all the time - Power usage 79-94 W when it suppose to be min 84 W > max 86 W or in this range
p.s. after 1 hour & half run i see this on pool: a drop on round progress from 0.007% to 0.004% because speed & my 1 cent bet because from what i see miner it not adjusting pool difficulty stay at max 100% time vs Klaus or Hsrminer what they doo soo a lose of 0.003% /round loss but i know it need to spend more time to see if is real or not ...
B. Equihash pass on testing coz today i not have time to watch excavator if it will crash or not. excavator_v1.4.1a_NVIDIA_Win64.zip it was done that in numerous time & for that i give up is like playing rusion rulet now is working fine now it decide to crash with noo particulary reason way frak know ... what i know is i can't let Excavator to mine with out watching what a hell he doing on this algoritm at all Dstm, EWBF, Bminer they work with out a problem in any pool, with out be watch ....
|
|
|
@dropky sorry i am confuse what's update ? 2 day agow 1.4.1.a > now you say new update but same version ? what's the catch ? & in other way 1.4.1.a Equihash still crash, stall & personaly i give up let a miner run & need to watch all the time because not know when it will crash is become ... - excavator_v1.4.1a_NVIDIA_Win64.zip = 8.0, 9.0 ??!?!?! - excavator_v1.4.1a_NVIDIA_Win64_CUDA_9.1.zip only with 9.1 ?!?!? anyway hope you will fix it in a future
|
|
|
Ocminer like a joke because your appi & site implementation problem if a Eve player (Eve online game) what it is use to relay on spreadsheet (exel) see how it work site for sure it will wardeck & chase on all galaxy possible 
|
|
|
@Ocminer Hello
Can you plssss plsss fix api & site data info coz for love o sake it bring so inaccurate data & nothing there it can be use:
- Round earnings est always value what is show it will never same in end not even close, most of time it show a bigger value what in end it is small - Round Progress % usual is stuck to a value no mater it refresh page 10 > 100 time - Worker activitie it need numerous try to open & close site from web browser to appear is working & show speed - Hasrage & Sharerate sometime are stuck with out refresh them self - Valid Share & Reject one i think is single part from appi, site what is functional or working - Graphs section random working most of time noo graphic showed for "mine" - Earnings value special All Time (total) or any value from there are just a random value what change on hell know base on what i was try to track them & very rare was same number like what suppose to be - Round Percentage % Last 24 Hours 203.34%, Last 7 Days 191.45%, Last 4 Weeks 198.31%, The Past 12 Months 168.32% realy ?!?!?! that number are most wieard & strange what i seen in many pools
I was try to test diferite mobile apps to monitor pool but because appi it working in strange way, same thing data what mobile app it bring they are most of time inaccurate, wrong
soo plssss fix it mobile app dev, miner need data / info in what can be trust other way anything is irrelevant & pointless
this thing is happen on btg, zen, zcash
cheers
|
|
|
That's quite cool. Thanks for the work! it was good if dear one he was say that application it require payment to  aka it gain $$$ is NOT FREE 
|
|
|
ping is messed up...use to get steady 52/53 ms now getting 200+ms since past couple days...whats going on here? us-east.equihash-hub.miningpoolhub.com Please help  all server are in Assia only 1 is in Germany but is working very badly ... check https://www.ipaddress.com & see your sefl way you have such a bad ping
|
|
|
Could somebody explain what is the difference between normal Nicehash app and this - Excavator  Nicehash application it use Excavator like default miner ... because it belong to Nicehash & is develop by them ... Nhm_setup_2.0.1.8 is a application / interface what track income, monitor & auto switch what is best to be mine according benchmark what you done on nicehash pool & it use Excavator miner, but it can use with out that for manual mining by ppls who not need to be told what's best do mine  chers
|
|
|
@miningpoolhub German European server = StatusDTS miner can't to connect, excavator same => server died or getting in strike not want to working - # connect to 139.162.138.168:20594 failed - net | Connecting to 139.162.138.168:20594 (139.162.138.168) - net | Connection lost! Reconnecting in 10 seconds Pinging 139.162.138.168 with 32 bytes of data: Reply from 139.162.138.168: bytes=32 time=39ms TTL=58 Reply from 139.162.138.168: bytes=32 time=39ms TTL=58 Reply from 139.162.138.168: bytes=32 time=39ms TTL=58 Reply from 139.162.138.168: bytes=32 time=39ms TTL=58 Reply from 139.162.138.168: bytes=32 time=39ms TTL=58
Ping statistics for 139.162.138.168: Packets: Sent = 5, Received = 5, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 39ms, Maximum = 39ms, Average = 39ms
Us server it start getting lagy to ... errr
|
|
|
Yeah... we haven't done any speed improvements on equihash in 1.3.9 version. What do you mean by "Excavator react strange sometime" when mining BTG? Do you get any error msgs?
Thanks for the feedback! We're constantly working on improving Excavator.
ok update 1.3.9.a mining BTG result in this: - Excavator window it became lagy switching between application (alt tab) it take few sec to be bring in front if was behind a browser let say - It generate huge amount of reject "low difficultie reason" , Zencash test run was perfect BTG nop is messy example: Est. Shares : 32,983,930 (done: 103.41%) Your Valid : 580.7254Your Invalid : 239.3974 (29.19%) TO MUCH Time Since Last Block: 40 minutes 21 seconds (round not done) & this is happen only with excavator dtsm working fine, i will check later Zcash to see
|
|
|
Hello & here it is feedback with new release:
Hardware Spec & setting:
GPU 0: Gigabyte Windforce 2 NVIDIA GeForce GTX 1060 3GB (Samsung) dedicate to mining GPU 1: Gigabyte NVIDIA GeForce GTX 650 2GB only for own use, not for mining OS: Windows 7 Service Pack 1 Video Driver: 390.65 MSI Afterburn: 4.4.2 Power limit: 72 => ~86 W Temp limit: 80 Core Clock: +168 Memmory Clock: +700 (i can be push to 920 but is good only for ETH)
A. Equihash Setting 2 worker set in Mode 0 because Mode 1 is waaaay slower aka bearly hit 255 sol/s, noo other extra parameter used
{"id":1,"method":"worker.add","params":["0","0","0"]}, {"id":1,"method":"worker.add","params":["0","0","0"]}
a. 1.3.8.a = 282 Sol/s & very rare it goo down to 278 b. 1.3.9.a = 282 Sol/s & very rare it goo down to 278
- equihash algo speed: 282 Sol/s = no improvement - running 2 hour farming Zencash, no crash / stall = good potential fix with new driver, need more time for testing, to be sure coz it was random - reject % reduce a lot! i seen my few on one round when in 1.3.8.a usual 10% was something normal = improvement - try to look on BTG coin it seams is something diferite vs other coin from this algoritm, Excavator react strange sometime Other miner speed:
- DSTM 0.5.8 = ~300 Sol/s - very rare reject - very stable i use full weak with out problem - EWBF 0.3.4b = 277 - 285 Sol/s - very rare reject - stable no issue
B. Neoscript default setting nothing change & test run was done on Feathercoin because is old & standard one
1.3.8.a B=603 (default) = 572 Kh/s => stable noo crash or stall 1.3.9.a B=603 (default) = 605 Kh/s => stable noo crash or stall
Other miner speed:
- Hsrminer by palginpav & alexkap = 710 - 720 Kh/s - Nsgminer 0.9.4 = 670 - 720 Kh/s - Ccminer KlausT 8.18 cuda 9.1 = 643 Kh/s
- speed small improvement & it can be done much more for sure
cheers
|
|
|
Hi guys is there any way to connect this miner to nicehash legacy? if there is please help for setup. thank you.
do mean mine on nicehash with dstm's ? . stratum+tcp://equihash.usa.nicehash.com:3357 or for SSL connection: stratum+ssl://equihash.usa.nicehash.com:33357 username: YourBitcoinAddress password: x either port works. nop he want to can use nicehash legacy app with dtsm but for that it require some deep file modification & some much more coding, depend how much nicehash team was hard lock there app But best for him is to goo on https://github.com/nicehash/NiceHashMinerLegacy & open a new Issue & request Dstm to be add
|
|
|
For the EU server, use the IP (don't use the fqdn!): 139.162.138.168 ... you're welcome, I don't want any bitcoins  Anyone knows if ETN is working for auto-switch on cryptonight? Only monero shows a port. dear one 139.162.138.168 is server what was or is on Germany & what i say it just died or stop working it was not respond at any trace, ping from me or any other site what it can back trace ip ... now i check agen & it semns it get try be alive high ping replay but at list it not say time out or not been found ... same whats point have dns like "europe.equihash-hub.miningpoolhub.com" what behind there are 5 server 2 in Japan, 2 in Singapore & 1 on Germany ... my geography, geolocation it fail getting in a infinite loop error or my be europe was moved to Japan  & i was not know :p
|
|
|
Hello @miningpoolhub can pls in name of all Gods to fix EU server!!!!  what end to be in Japan & Singapore = mining with 300-400 mls is not good & last EU server it sems is stop working aka that one from Germany just died, kaput !!! Atm for eu ppls is better to mine on US server coz at list it bring ~150 mls so FIX EU server is past around 1 week from when this happen thx
|
|
|
hello @dstm can you explain way zm is stay connected 100% of time to > XXXXX.ip-94-23-20.eu < first part of address i was remove ... anyone who use dstm it can see it in network activitie ...
if is a way to get your fee next question is way it stay 100% connected ?!?!?! & is not use only when fee it need to be take see how claymore done it !
cheers
ZM uses an additional connection (in addition to your pool-connection) to submit the dev-shares. For this zm uses currently one of the flypool servers (eu1-zcash.flypool.org, us1-zcash.flypool.org, asia1-zcash.flypool.org). ZM does not establish any connections to private servers and uses only public pool servers to submit the dev-shares. This is especially important since using connections to private servers allows the mining software to track/collect data about it's users - it would also allow the mining software to 'steal' shares which solve whole blocks. Well getting dev-share i get it. From tracing that extra ip what is use i already seen is part from public pool ( www.ipaddress.com tools, a perfect place to find good info) & that was reason way i use your apps & not use bminer! what it use some strange ip, plus it use 2 extra NOT only 1 ... But back to my initial point way miner it need to stay connect always? & it not use same technique like claymore use in his miner app aka: => dev share time => it connect to pool => it done what it need to be done => it disconnect letting run on initial pool, what it make to be very transparent & fine about dev fee i undested perfectly developing it require something in return for any dev time, i will not goo on road if is big fee or small ... but make it transparent  cheers
|
|
|
The version 5.1.0 has released: - Support NiceHash.
- Fix unstable network connections in 5.0.0.
- Fix performance regressions for 1080Ti under Linux.
Enjoy mining! New version same thing: Miner it use 2 extra internet connection 100% of time beside mining pool & appi so agen i will say pass on using this miner bminer.exe TCP 104.31.68.221 https bminer.exe TCP gre14.anti-ddos.pro 6633
|
|
|
Hello GPU: Gigabyte Windforce 2 NVIDIA GeForce GTX 1060 3GB (Samsung) OS: Windows 7 Service Pack 1 Video Driver: 390.65 MSI Afterburn: 4.4.2 Gateless_Gate_Sharp_1.1.16_alpha = Last test https://bitcointalk.org/index.php?topic=1716584.msg27601822#msg27601822Gateless_Gate_Sharp_1.2.2_alpha = New Test done to check progression Let's begin: 1. Application is very lagy old test > new test same = no improvement- Pressing Start button action is take after 10-15 sec - Pressing Stop it take between 10-25 sec program to fully stop from mining & stop using video card (i was watching MSI Afb) - Closing program it take near 30-40 sec action to be done, all this time GSS windows is not responsive 2. Dashboard = not functional (custom pool used for testing) Elapsed Time: not working, noo time pass Speed: 0 all the time, algo used is correctly reported Device Speed not working, Share not working, Core not working, Mem Not working Single place were it can see any activity is "Log Tab" = speed, share are seen 3. Eror 2018-01-14 12:58:46.0756 [1] Exception in InitializeDevices(): Object reference not set to an instance of an object. at GatelessGateSharp.OpenCLDevice.get_DefaultCoreClock() at GatelessGateSharp.MainForm.ResetDeviceOverclockingSettings(Device device) at GatelessGateSharp.MainForm.InitializeDevices() at GatelessGateSharp.MainForm.MainForm_Load(Object sender, EventArgs e) 4. Second GPU is incorrectly detect, is not a problem coz is not meant for mining but still is a bug, a 650 GTX for personal necessitate 5. GSS still have warning about want windows swap to be set at 24 G & noo disable / ignore option implement with is bad request 6. Msi Afterburner is not happy at all & somehow i think GSS it overight or try to gain control, ignoring setting already done, with is BAD, special if OC is not enable at all, GPU clock, Memory clock out of chart or of limit what suppose to be = BAD 7. Mining speed i will not say anything because i undestend from your previous replay GSS is not tune for Nvidia soo i will ignore this part cheers
|
|
|
hello @dstm can you explain way zm is stay connected 100% of time to > XXXXX.ip-94-23-20.eu < first part of address i was remove ... anyone who use dstm it can see it in network activitie ...
if is a way to get your fee next question is way it stay 100% connected ?!?!?! & is not use only when fee it need to be take see how claymore done it !
cheers
|
|
|
Hello @Epsylon3 I done some testing with CCminer 2.2.1, 2.2.2, 2.2.3, 2.2.4 & i was get something interesting with equihash algoritm GPU: Gigabyte Windforce 2 NVIDIA GeForce GTX 1060 3GB (Samsung) Video Driver: 388.71 OS: Windows 7 Service Pack 1 Msi Afterburner 4.4.2 Power Limit: 72% (86W) Core Clock: +170 VRam Clock: +450 (not relevant for this algorit) - Ccminer it make GPU clock usage to be: 1900-1940 Mhz with Power: 85-86W what result in 258-260 Sol/s - Excavator v.1.3.8.a 1830-1880 Mhz with Power: 85-86W what result in ~280 Sol/s - DTMS 5.8 GPU clock it goo to: 1830-1880 Mhz with Power: 85-86W what result in ~300 Sol/s Well now what i will like to get is to see CCminer running on ~1900 Mhz with 86W on +300 Sol/s!!! so a tune like that can be that done in a future update ? if yes it will be damn greats  cheers
|
|
|
any monitoring http protocol or soft for this? I'm struggling with ewbf + it has no more updates, would like to switch to another one with centralized monitoring
see README.txt file & you want to switch from EWBF because gain more speed & more hpower to  try use this: --telemetry [=ip:port]. Starts telemetry server. Telemetry data can be accessed using a web browser(http) or by json-rpc. If no arguments are given the server listens on 127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222 Valid port range [1025-65535]
there are other option to combine with this miner app but way not keep thing simple  cheers
|
|
|
how to mine with ZM using only xyz GPU card?
If u have 5 GUPS and only want to use GPU 1-3
what is the syntax / command for this , please?
for select what gpu you want to use > --dev number < is what you need to add in command line, if you was read README.txt is there  - first run zm --list-devices to see how gpu are listed then - aka if you want to use gpu 1 2 3 then: --dev 0 1 2 you need to use or a combo like that see first step cheers
|
|
|
|