But the tabs "Miner" and "Admin" are still empty for me.
I have sent 0.42 BTC to 1Btf3BqUegfe5iFdWsgfBf1Ew3YsAvsrLT for motivational purposes.
Topic: BTCMiner - Open Source Bitcoin Miner for ZTEX FPGA Boards, 215 MH/s on LX150 - page 6. (Read 161510 times)
November 10, 2012, 12:20:50 PM
Thank you. The workaround did the trick.
But the tabs "Miner" and "Admin" are still empty for me.
I have sent 0.42 BTC to 1Btf3BqUegfe5iFdWsgfBf1Ew3YsAvsrLT for motivational purposes.
But the tabs "Miner" and "Admin" are still empty for me.
I have sent 0.42 BTC to 1Btf3BqUegfe5iFdWsgfBf1Ew3YsAvsrLT for motivational purposes.
November 10, 2012, 11:39:18 AM
Thank you for your help. The webinterface is running now. I didn't use the httpd-cluster mode.
But I have the problem that no shares are submitted. I am using your newest jar. It makes no difference if I start it with or without the "-tc" parameter.
In the webinterface the tabs "miners" and "admin" are empty.
Any ideas?
But I have the problem that no shares are submitted. I am using your newest jar. It makes no difference if I start it with or without the "-tc" parameter.
In the webinterface the tabs "miners" and "admin" are empty.
Quote
java -cp ZtexBTCMiner.jar BTCMiner -m h -p 7005 -ac 7200 -nolog -oh 0.1 -n 6 -tc -o Slush https://mining.bitcoin.cz/stats/ http://api.bitcoin.cz:8332 user pass
Any ideas?
Seem's that you have encountered a bug. The pool is not active. A quick fix: click on the pool number on the Mining pools tab. Another advice, add a backup pool with option -b.
The option -n 6 is a nice have for my setup to distibute all miner equally to the mining threads. -nolog disables log file writing. -p 7005 is the httpd port number.
I will fix the bug later... have to leave now.
November 10, 2012, 11:23:53 AM
Thank you for your help. The webinterface is running now. I didn't use the httpd-cluster mode.
But I have the problem that no shares are submitted. I am using your newest jar. It makes no difference if I start it with or without the "-tc" parameter.
In the webinterface the tabs "miners" and "admin" are empty.
Any ideas?
But I have the problem that no shares are submitted. I am using your newest jar. It makes no difference if I start it with or without the "-tc" parameter.
In the webinterface the tabs "miners" and "admin" are empty.
Quote
java -cp ZtexBTCMiner.jar BTCMiner -m h -p 7005 -ac 7200 -nolog -oh 0.1 -n 6 -tc -o Slush https://mining.bitcoin.cz/stats/ http://api.bitcoin.cz:8332 user pass
Any ideas?
November 10, 2012, 11:07:14 AM
grobi42: Thanks you for the fancy webinterface. I am running the miner on a QNAP NAS. But the Webserver doesn't start up. Are there any logs where I can see why ?
edit: typo
edit: typo
Did you start the miner in httpd-cluster mode (option -m h instead -m c)?
Here's the startup script I'm using (replace user and pass, maybe the website url too):
Code:
#!/bin/sh
java -cp ZtexBTCMiner.jar BTCMiner -m h -id Ztex1 -p 7005 -ac 7200 -nolog -oh 0.1 -n 6 -tc \
-o "Slush (Stratum)" https://mining.bitcoin.cz/stats/ http://192.168.1.200:8332 user pass \
-o "BtcGuild (Stratum)" http://www.btcguild.com/my_account.php http://192.168.1.200:9332 user pass \
-o MtRed https://mtred.com/user/profile.html http://mtred.com:8337 user pass \
-o Itzod http://pool.itzod.ru/index.php http://pool.itzod.ru:8346 user pass \
-o Bitminter http://bitminter.com http://mint.bitminter.com:8332 user pass \
-o Ozcoin http://ozco.in http://eu.ozco.in:80 user pass \
-o 50Btc https://50btc.com/account http://50btc.com:8332 user pass \
-b Ozcoin http://ozco.in http://eu.ozco.in:80 user pass \
-b 50Btc https://50btc.com/account http://50btc.com:8332 user pass \
-b "BtcGuild (Stratum)" http://www.btcguild.com/my_account.php http://192.168.1.200:9332 user pass
java -cp ZtexBTCMiner.jar BTCMiner -m h -id Ztex1 -p 7005 -ac 7200 -nolog -oh 0.1 -n 6 -tc \
-o "Slush (Stratum)" https://mining.bitcoin.cz/stats/ http://192.168.1.200:8332 user pass \
-o "BtcGuild (Stratum)" http://www.btcguild.com/my_account.php http://192.168.1.200:9332 user pass \
-o MtRed https://mtred.com/user/profile.html http://mtred.com:8337 user pass \
-o Itzod http://pool.itzod.ru/index.php http://pool.itzod.ru:8346 user pass \
-o Bitminter http://bitminter.com http://mint.bitminter.com:8332 user pass \
-o Ozcoin http://ozco.in http://eu.ozco.in:80 user pass \
-o 50Btc https://50btc.com/account http://50btc.com:8332 user pass \
-b Ozcoin http://ozco.in http://eu.ozco.in:80 user pass \
-b 50Btc https://50btc.com/account http://50btc.com:8332 user pass \
-b "BtcGuild (Stratum)" http://www.btcguild.com/my_account.php http://192.168.1.200:9332 user pass
Read the README for more details, or start BTCMiner with option -h to get a description of all options.
Some Website hints:
On the pool tab:
you can switch the pools by clicking on the pool number
you can open the pools website by clicking on the pools name
and if you click on the "Ztex1@fpga:7005" you can force and update.
So long
November 10, 2012, 09:52:56 AM
grobi42: Thanks you for the fancy webinterface. I am running the miner on a QNAP NAS. But the Webserver doesn't start up. Are there any logs where I can see why ?
edit: typo
edit: typo
November 09, 2012, 08:27:23 AM
A new Bugfix version is available here: https://github.com/downloads/gr0bi42/BTCMiner/ZtexBTCMiner_gr0bi42_20121109.tar.bz2
Changes: bugfix - with disabled target checking, no shares were submitted *doh*
Changes: bugfix - with disabled target checking, no shares were submitted *doh*
November 08, 2012, 12:44:56 PM
A new testing version has been released.
Binaries: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.jar
Source: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.tar.bz2
New features are:
* Temperature sensor support for USB-FPGA Modules 1.15y rev. 2 (temperature limit is set using the paramter -t)
* X-Mining-extensions: midstate, submitold
* Target checking, must be enabled using -tc
* MAC address printed at -i
Binaries: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.jar
Source: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.tar.bz2
New features are:
* Temperature sensor support for USB-FPGA Modules 1.15y rev. 2 (temperature limit is set using the paramter -t)
* X-Mining-extensions: midstate, submitold
* Target checking, must be enabled using -tc
* MAC address printed at -i
Hi,
I've integrated the recent changes into my httpd version of BTCMiner.
Source is online here: https://github.com/gr0bi42/BTCMiner
Made some changes regarding target checking too, although there are still problems with pool.itzod.ru.
Added a cool looking JSON based Webinterface. See photos below.
Precompiled package is available here: https://github.com/downloads/gr0bi42/BTCMiner/ZtexBTCMiner_gr0bi42_20121108.tar.bz2
See the README for further infos.
Happy mining
Edit: lower resolution screenshots (was a retina display side effect)
October 19, 2012, 04:03:01 AM
What is target checking good for?
I'll have to try it this night
I'll have to try it this night
See https://en.bitcoin.it/wiki/Target, if pool difficulty is > 1 it only submits shares that met the target. (By default all shares smaller then the maximum target are submitted).
October 19, 2012, 03:53:48 AM
Total hash rate: 3398,6 MH/s
Total submitted hash rate: 3418,7 MH/s
--------
works great - i have arround 200 MH/s more submitted shares with 2 quads.
2 questions -
how to set the temp option exactly and - which temp range is ok for the quads
Total submitted hash rate: 3418,7 MH/s
--------
works great - i have arround 200 MH/s more submitted shares with 2 quads.
2 questions -
how to set the temp option exactly and - which temp range is ok for the quads
The temperature limit is set using the parameter -t, e.g. -t 65 sets it to 65°C. If this temperature is reached the FPGA is shut down.
Up to 70°C (default temperature limit) is ok. But try to stay below 60°C in order to achieve the maximum performance.
October 18, 2012, 03:29:19 PM
What is target checking good for?
I'll have to try it this night
tried it on p2pool sseing this:
I'll have to try it this night
tried it on p2pool sseing this:
Code:
bus-0-0: ztex_ufm1_15d4-04A32E1205-1: f=204,00MHz, errorRate=0,07%, maxErrorRate=0,90%, hashRate=203,9MH/s, submitted 16 new nonces, luckFactor=1,21
bus-0-0: ztex_ufm1_15d4-04A3468E00-1: f=208,00MHz, errorRate=0,07%, maxErrorRate=0,86%, hashRate=207,9MH/s, submitted 16 new nonces, luckFactor=0,97
bus-0-0: ztex_ufm1_15d4-04A3469756-1: f=212,00MHz, errorRate=0,41%, maxErrorRate=1,25%, hashRate=211,1MH/s, submitted 15 new nonces, luckFactor=0,87
bus-0-0: ztex_ufm1_15d4-04A346BF8B-1: f=212,00MHz, errorRate=0,03%, maxErrorRate=0,71%, hashRate=211,9MH/s, submitted 14 new nonces, luckFactor=1,00
bus-0-0: ztex_ufm1_15d4-04A346D523-1: f=216,00MHz, errorRate=0,02%, maxErrorRate=0,50%, hashRate=216,0MH/s, submitted 17 new nonces, luckFactor=1,02
bus-0-0: ztex_ufm1_15d4-04A346E12C-1: f=204,00MHz, errorRate=1,17%, maxErrorRate=2,36%, hashRate=201,6MH/s, submitted 18 new nonces, luckFactor=1,22
bus-0-0: ztex_ufm1_15y1-04A3461185-1: f=228,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=228,0MH/s, submitted 10 new nonces, luckFactor=0,57
bus-0-0: ztex_ufm1_15y1-04A3461185-2: f=228,00MHz, errorRate=0,68%, maxErrorRate=1,36%, hashRate=226,4MH/s, submitted 20 new nonces, luckFactor=0,93
bus-0-0: ztex_ufm1_15y1-04A3461185-3: f=228,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=228,0MH/s, submitted 14 new nonces, luckFactor=0,89
bus-0-0: ztex_ufm1_15y1-04A3461185-4: f=228,00MHz, errorRate=0,13%, maxErrorRate=0,51%, hashRate=227,7MH/s, submitted 10 new nonces, luckFactor=0,91
bus-0-1: ztex_ufm1_15y1-04A34644C6-1: f=220,00MHz, errorRate=0,00%, maxErrorRate=1,00%, hashRate=220,0MH/s, submitted 12 new nonces, luckFactor=0,80
bus-0-1: ztex_ufm1_15y1-04A34644C6-2: f=228,00MHz, errorRate=0,07%, maxErrorRate=0,82%, hashRate=227,8MH/s, submitted 8 new nonces, luckFactor=0,69
bus-0-1: ztex_ufm1_15y1-04A34644C6-3: f=224,00MHz, errorRate=0,00%, maxErrorRate=0,94%, hashRate=224,0MH/s, submitted 14 new nonces, luckFactor=0,80
bus-0-1: ztex_ufm1_15y1-04A34644C6-4: f=228,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=228,0MH/s, submitted 15 new nonces, luckFactor=0,93
bus-0-1: ztex_ufm1_15y1-04A36E24F2-1: f=220,00MHz, errorRate=0,74%, maxErrorRate=1,32%, hashRate=218,4MH/s, submitted 15 new nonces, luckFactor=1,03
bus-0-1: ztex_ufm1_15y1-04A36E24F2-2: f=216,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=216,0MH/s, submitted 21 new nonces, luckFactor=1,12
bus-0-1: ztex_ufm1_15y1-04A36E24F2-3: f=220,00MHz, errorRate=0,00%, maxErrorRate=0,98%, hashRate=220,0MH/s, submitted 24 new nonces, luckFactor=1,06
bus-0-1: ztex_ufm1_15y1-04A36E24F2-4: f=216,00MHz, errorRate=0,75%, maxErrorRate=1,03%, hashRate=214,4MH/s, submitted 21 new nonces, luckFactor=1,09
bus-0-0: poll loop time: 49ms (USB: 46ms network: 3ms) getwork time: 7ms submit time: 2ms
bus-0-1: poll loop time: 51ms (USB: 49ms network: 3ms) getwork time: 8ms submit time: 3ms
Total hash rate: 3931,1 MH/s
Total submitted hash rate: 3699,5 MH/s
--------
bus-0-0: ztex_ufm1_15y1-04A3461185-1: Set frequency from 228,00MHz to 232,00MHz
New block detected by long polling (submitold = true)
New block detected by long polling (submitold = true)
New block detected by long polling (submitold = true)
bus-0-0: ztex_ufm1_15y1-04A3461185-1: Set frequency from 232,00MHz to 228,00MHz
New block detected by long polling (submitold = true)
New block detected by long polling (submitold = true)
bus-0-0: ztex_ufm1_15d4-04A3468E00-1: f=208,00MHz, errorRate=0,07%, maxErrorRate=0,86%, hashRate=207,9MH/s, submitted 16 new nonces, luckFactor=0,97
bus-0-0: ztex_ufm1_15d4-04A3469756-1: f=212,00MHz, errorRate=0,41%, maxErrorRate=1,25%, hashRate=211,1MH/s, submitted 15 new nonces, luckFactor=0,87
bus-0-0: ztex_ufm1_15d4-04A346BF8B-1: f=212,00MHz, errorRate=0,03%, maxErrorRate=0,71%, hashRate=211,9MH/s, submitted 14 new nonces, luckFactor=1,00
bus-0-0: ztex_ufm1_15d4-04A346D523-1: f=216,00MHz, errorRate=0,02%, maxErrorRate=0,50%, hashRate=216,0MH/s, submitted 17 new nonces, luckFactor=1,02
bus-0-0: ztex_ufm1_15d4-04A346E12C-1: f=204,00MHz, errorRate=1,17%, maxErrorRate=2,36%, hashRate=201,6MH/s, submitted 18 new nonces, luckFactor=1,22
bus-0-0: ztex_ufm1_15y1-04A3461185-1: f=228,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=228,0MH/s, submitted 10 new nonces, luckFactor=0,57
bus-0-0: ztex_ufm1_15y1-04A3461185-2: f=228,00MHz, errorRate=0,68%, maxErrorRate=1,36%, hashRate=226,4MH/s, submitted 20 new nonces, luckFactor=0,93
bus-0-0: ztex_ufm1_15y1-04A3461185-3: f=228,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=228,0MH/s, submitted 14 new nonces, luckFactor=0,89
bus-0-0: ztex_ufm1_15y1-04A3461185-4: f=228,00MHz, errorRate=0,13%, maxErrorRate=0,51%, hashRate=227,7MH/s, submitted 10 new nonces, luckFactor=0,91
bus-0-1: ztex_ufm1_15y1-04A34644C6-1: f=220,00MHz, errorRate=0,00%, maxErrorRate=1,00%, hashRate=220,0MH/s, submitted 12 new nonces, luckFactor=0,80
bus-0-1: ztex_ufm1_15y1-04A34644C6-2: f=228,00MHz, errorRate=0,07%, maxErrorRate=0,82%, hashRate=227,8MH/s, submitted 8 new nonces, luckFactor=0,69
bus-0-1: ztex_ufm1_15y1-04A34644C6-3: f=224,00MHz, errorRate=0,00%, maxErrorRate=0,94%, hashRate=224,0MH/s, submitted 14 new nonces, luckFactor=0,80
bus-0-1: ztex_ufm1_15y1-04A34644C6-4: f=228,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=228,0MH/s, submitted 15 new nonces, luckFactor=0,93
bus-0-1: ztex_ufm1_15y1-04A36E24F2-1: f=220,00MHz, errorRate=0,74%, maxErrorRate=1,32%, hashRate=218,4MH/s, submitted 15 new nonces, luckFactor=1,03
bus-0-1: ztex_ufm1_15y1-04A36E24F2-2: f=216,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=216,0MH/s, submitted 21 new nonces, luckFactor=1,12
bus-0-1: ztex_ufm1_15y1-04A36E24F2-3: f=220,00MHz, errorRate=0,00%, maxErrorRate=0,98%, hashRate=220,0MH/s, submitted 24 new nonces, luckFactor=1,06
bus-0-1: ztex_ufm1_15y1-04A36E24F2-4: f=216,00MHz, errorRate=0,75%, maxErrorRate=1,03%, hashRate=214,4MH/s, submitted 21 new nonces, luckFactor=1,09
bus-0-0: poll loop time: 49ms (USB: 46ms network: 3ms) getwork time: 7ms submit time: 2ms
bus-0-1: poll loop time: 51ms (USB: 49ms network: 3ms) getwork time: 8ms submit time: 3ms
Total hash rate: 3931,1 MH/s
Total submitted hash rate: 3699,5 MH/s
--------
bus-0-0: ztex_ufm1_15y1-04A3461185-1: Set frequency from 228,00MHz to 232,00MHz
New block detected by long polling (submitold = true)
New block detected by long polling (submitold = true)
New block detected by long polling (submitold = true)
bus-0-0: ztex_ufm1_15y1-04A3461185-1: Set frequency from 232,00MHz to 228,00MHz
New block detected by long polling (submitold = true)
New block detected by long polling (submitold = true)
Code:
2012-10-19 00:25:32.438000 P2Pool: 17421 shares in chain (9537 verified/17425 total) Peers: 14 (4 incoming)
2012-10-19 00:25:32.439000 Local: 3736MH/s in last 10.0 minutes Local dead on arrival: ~4.2% (2-7%) Expected time to share: 13.1 minutes
2012-10-19 00:25:32.440000 Shares: 7 (1 orphan, 3 dead) Stale rate: ~57.1% (25-85%) Efficiency: ~49.2% (18-86%) Current payout: 0.0174 BTC
2012-10-19 00:25:32.441000 Pool: 353GH/s Stale rate: 12.8% Expected time to block: 10.4 hours
2012-10-19 00:25:32.439000 Local: 3736MH/s in last 10.0 minutes Local dead on arrival: ~4.2% (2-7%) Expected time to share: 13.1 minutes
2012-10-19 00:25:32.440000 Shares: 7 (1 orphan, 3 dead) Stale rate: ~57.1% (25-85%) Efficiency: ~49.2% (18-86%) Current payout: 0.0174 BTC
2012-10-19 00:25:32.441000 Pool: 353GH/s Stale rate: 12.8% Expected time to block: 10.4 hours
October 18, 2012, 12:17:32 PM
sorry - 4 quads !
October 18, 2012, 11:21:02 AM
Total hash rate: 3398,6 MH/s
Total submitted hash rate: 3418,7 MH/s
--------
works great - i have arround 200 MH/s more submitted shares with 2 quads.
2 questions -
how to set the temp option exactly and - which temp range is ok for the quads
Total submitted hash rate: 3418,7 MH/s
--------
works great - i have arround 200 MH/s more submitted shares with 2 quads.
2 questions -
how to set the temp option exactly and - which temp range is ok for the quads
what?!! so many MH/s with only 2 quads??? can you tell me more about your mining soft & hardware.
October 18, 2012, 10:48:30 AM
Total hash rate: 3398,6 MH/s
Total submitted hash rate: 3418,7 MH/s
--------
works great - i have arround 200 MH/s more submitted shares with 2 quads.
2 questions -
how to set the temp option exactly and - which temp range is ok for the quads
Total submitted hash rate: 3418,7 MH/s
--------
works great - i have arround 200 MH/s more submitted shares with 2 quads.
2 questions -
how to set the temp option exactly and - which temp range is ok for the quads
October 17, 2012, 10:20:51 AM
A new testing version has been released.
Binaries: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.jar
Source: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.tar.bz2
New features are:
* Temperature sensor support for USB-FPGA Modules 1.15y rev. 2 (temperature limit is set using the paramter -t)
* X-Mining-extensions: midstate, submitold
* Target checking, must be enabled using -tc
* MAC address printed at -i
Binaries: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.jar
Source: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.tar.bz2
New features are:
* Temperature sensor support for USB-FPGA Modules 1.15y rev. 2 (temperature limit is set using the paramter -t)
* X-Mining-extensions: midstate, submitold
* Target checking, must be enabled using -tc
* MAC address printed at -i
October 17, 2012, 10:14:55 AM
By the way... any chance to see Stratum soon in BTCMiner?
See https://bitcointalksearch.org/topic/m.1244118
October 15, 2012, 05:51:45 AM
By the way... any chance to see Stratum soon in BTCMiner?
October 09, 2012, 06:42:18 AM
Hi,
after testing the Ztex 1.15x on CGMiner (and really not liking the experience.. unfortunately) i tried to get back on BTCMiner but i have a problem:
I cant find a way to revive it for BTCMiner... CGMiner still works "fine" (as in the limits set by CGMiner) though..
Any ideas?
after testing the Ztex 1.15x on CGMiner (and really not liking the experience.. unfortunately) i tried to get back on BTCMiner but i have a problem:
Code:
C:\ztex>java -cp ZtexBTCMiner-120703.jar BTCMiner -host "http://de.btcguild.com:8332" -u Nachtwind_fpga -p yup -f ztex_ufm1_15d4.ihx
Error: Device lost after uploading Firmware: No new device found
Error: Device lost after uploading Firmware: No new device found
I cant find a way to revive it for BTCMiner... CGMiner still works "fine" (as in the limits set by CGMiner) though..
Any ideas?
Did you change the usb driver back ? IIRC you can do that with Zadig.
*edit*
Ok, changing the driver to libusb did the trick. Thanks.
October 09, 2012, 06:37:19 AM
Hi,
after testing the Ztex 1.15x on CGMiner (and really not liking the experience.. unfortunately) i tried to get back on BTCMiner but i have a problem:
I cant find a way to revive it for BTCMiner... CGMiner still works "fine" (as in the limits set by CGMiner) though..
Any ideas?
after testing the Ztex 1.15x on CGMiner (and really not liking the experience.. unfortunately) i tried to get back on BTCMiner but i have a problem:
Code:
C:\ztex>java -cp ZtexBTCMiner-120703.jar BTCMiner -host "http://de.btcguild.com:8332" -u Nachtwind_fpga -p yup -f ztex_ufm1_15d4.ihx
Error: Device lost after uploading Firmware: No new device found
Error: Device lost after uploading Firmware: No new device found
I cant find a way to revive it for BTCMiner... CGMiner still works "fine" (as in the limits set by CGMiner) though..
Any ideas?
Did you change the usb driver back ? IIRC you can do that with Zadig.
October 09, 2012, 05:01:16 AM
Hi,
after testing the Ztex 1.15x on CGMiner (and really not liking the experience.. unfortunately) i tried to get back on BTCMiner but i have a problem:
I cant find a way to revive it for BTCMiner... CGMiner still works "fine" (as in the limits set by CGMiner) though..
Any ideas?
after testing the Ztex 1.15x on CGMiner (and really not liking the experience.. unfortunately) i tried to get back on BTCMiner but i have a problem:
Code:
C:\ztex>java -cp ZtexBTCMiner-120703.jar BTCMiner -host "http://de.btcguild.com:8332" -u Nachtwind_fpga -p yup -f ztex_ufm1_15d4.ihx
Error: Device lost after uploading Firmware: No new device found
Error: Device lost after uploading Firmware: No new device found
I cant find a way to revive it for BTCMiner... CGMiner still works "fine" (as in the limits set by CGMiner) though..
Any ideas?
October 04, 2012, 06:32:38 AM
@ztex its not about bandwidth but stales...
@deeplink thanks!
@deeplink thanks!
Jump to: