Bitcoin Forum
May 28, 2024, 01:58:46 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 [6] 7 8 9 10 11 »
101  Bitcoin / Mining / Re: Is "casual" mining still sustainable? Is buying a new rig stupid? on: July 27, 2011, 08:45:16 PM
keep in mind 95% of the population is absolutely *retarded* about managing finances.

+1

Anyone who pays 15% (or more) interest on a credit card balance is pretty bad with money. And that's a *lot* of people.
It's even worse if they charged up stuff because it was "on sale", not realizing they'll pay much more for it in the long run.


Yeah, I know what you mean. I just finished paying off 24K of credit cards this year and got out of my house via short sale. Feels good to be free. FREE!!!! HAHAHAHAHA! NO MORE DEBT!! Cheesy
102  Other / Archival / Re: Pictures of your mining rigs! on: July 27, 2011, 07:00:03 PM
I know from experience, acrid electrical smoke and burnt electronics, that when you expect an outlet to be 120v because of the connector and you plug a 120v switched device into a 240v plug you're just kinda screwed. Best to have the 120v as C13 and 240v as C14. Makes life easier. The power distribution on my rack all runs C14 for this reason.

Their really isn't anything I can do about the fact that all the commonly available PSU's terminate in a C13 socket. All the better brands auto switch to 240v, and they all come with C13 sockets, not C14.

The male plug ends are NEMA 6-15 which is physically impossible to plug a stand NEMA 5-15 120V cord into, so it's not possible to accidentally plug something else into the 240v outlet. The only possibility for mistake is if you unplugged the C13 end of the cord from the mining rig and plugged it into another  device which can't handle 240v. Which isn't going to happen.

Basicily if it's good end for Corsair, and it's good enough for the Underwriters Laboratory it's good enough for me.




Well, the PSU terminates in a C13 but the other end of the cable is what I'm talking about. The C14 that looks like a reversed plug with a shroud around it is specifically 240v. But whatever works for you, all good. Just speaking from my experience with electronics destruction I prefer to keep plug types separate.
103  Bitcoin / Mining software (miners) / Re: Flexible mining proxy on: July 26, 2011, 11:25:45 PM

I love what you're doing... that's awesome.. for my 2cents, I'd like to see the temps/load/etc separated from the "worker" name, since multiGPU boxes will generally run (1) worker per box... more than that gets unmanagable quickly.

Either that or you poll all the GPU's/CPU/etc in the box, and log the average..

Glad you enjoy it Smiley

In regard to separating the workers.. well, that's not really possible with the current schema. Also I'm not sure it makes sense to store multiple GPU device temperature stats for one worker. It would require a 1:N schema which would require a completely different approach for the monitoring script, schema, and reporting aspects as well as graphing. You can get around this by making dummy workers in the proxy and having the health monitor script upload it's data for those dummy workers. So your single-worker-per-box can connect to the proxy as usual, but you'd have like "box-name-GPU0", "box-name-GPU1" etc and look at the graphs that way. But I can't store multiple GPU temperatures for a single worker.

As to administrative hassle of multiple workers per box, my boxes are all running 3-4 cards each with one instance of phoenix per GPU. Having an aggregate worker for all devices on a box makes it very difficult to see how an individual GPU is performing, and Phoenix can't use multiple devices per process instance. The only miner I know that will use multiple devices is Diablo, which runs about 5-10% slower on my GPUs than Phoenix.

Managing multiple devices per box is actually very simple, I have a script per instance that gets started via the LXDE autostart script:

Code:
> cat /etc/xdg/lxsession/LXDE/autostart
@lxpanel --profile LXDE
@pcmanfm --desktop --profile LXDE
@sleep 3
@/usr/bin/screen -dmS proxy0 /home/user/p0.sh
@/usr/bin/screen -dmS proxy1 /home/user/p1.sh
@/usr/bin/screen -dmS proxy2 /home/user/p2.sh
@/usr/bin/screen -dmS monitor /bin/ping 172.16.0.1
@lxterminal

Each of the /home/user/p<GPU_DEVICE_NUMBER>.sh script contains the following code to start up fans, core/mem speed, and connect to flexible proxy. If I reboot the box the miners get started automatically without any input from me. If my UPS dies the BIOS on each server is set to restore power to "LAST STATE", so they will turn on as soon as there is power available, then they boot LinuxCoin into init-level-5 and run the autostart script which in turn runs the miner via this code:

Code:
#!/bin/sh
#6870 OC Settings
CLOCK_CPU=950
CLOCK_MEM=1050
FANSPEED=100
WORKSIZE=128
AGGRESSION=11
DEVICE="0"
LOG="/home/user/log.$DEVICE.out"
URL="<flexible_proxy_ip_address>"
PORT="80"
USER="box#gpu#" #Worker naming schema: server_name<server-number>c<GPU#> like: ultra0gpu2 for "sun ultra40 workstation number zero, gpu device two"
PASS="password"

export DISPLAY=:0.$DEVICE
aticonfig --od-enable
echo "running: aticonfig --od-setclocks=$CLOCK_CPU,$CLOCK_MEM --adapter=$DEVICE"
aticonfig --od-setclocks=$CLOCK_CPU,$CLOCK_MEM --adapter=$DEVICE
aticonfig --odgt --adapter=$DEVICE
aticonfig --pplib-cmd "get fanspeed 0"
aticonfig --odgc --adapter=$DEVICE
aticonfig --pplib-cmd "set fanspeed 0 $FANSPEED"
aticonfig --pplib-cmd "get fanspeed 0"
echo "running: ./phoenix.py --url=http://${USER}:${PASS}@$URL:$PORT -k phatk VECTORS BFI_INT FASTLOOP=false WORKSIZE=$WORKSIZE AGGRESSION=$AGGRESSION DEVICE=$DEVICE"
python ./phoenix.py --logtotext=$LOG --url=http://${USER}:${PASS}@$URL:$PORT -k phatk VECTORS BFI_INT FASTLOOP=false WORKSIZE=$WORKSIZE AGGRESSION=$AGGRESSION DEVICE=$DEVICE

104  Bitcoin / Mining software (miners) / Re: Flexible mining proxy on: July 26, 2011, 10:57:40 PM
I added support for graphing temperature. There's a link for each worker on the "temp" column which will show you the last 24 hours of temperatures for each card....

How tough would it be to add graphs for both "worker" and "aggregate" mining data, like Mhash, shares, rejects, etc?



I'll have to look at the schema tables that store that data. Once I get a query to support gathering the data over time then pushing it to the graphing system is trivial. I'll update my findings soon.
105  Other / Archival / Re: Pictures of your mining rigs! on: July 26, 2011, 05:13:15 PM
...was to switch them over to 240v. I'm in an appartment, so my options are limited, but I was able to plugin to the 40AMP 240V outlet for my electric stove...
Where do you find a 240v adapter for the PSUs?

Or did you stay at 120v and use something like this?

http://www.amazon.com/Jard-Magnetics-10048PC-Fully-Isolated-Transformer/dp/B003AT7CJ0

Nope. The corsair AX1200 I use automatically switches to 240v, and about %4 more efficient at the higher voltage (their stats, I don't have a 240v amp meter)

http://www.horticulturesource.com/hydrofarm-240-volt-8-ballast-power-cord-p6174/?osCsid=87326d44bee99fdc1dd1801cd8383fc3

The same store sells a quality made three socket 240v extension cord too..

I wouldn't recommend mixing 120v style cords in a 240v power environment. In general, datacenters run C14 power cords for 240v systems: http://www.newegg.com/Product/Product.aspx?Item=N82E16812115051&nm_mc=OTC-Froogle&cm_mmc=OTC-Froogle-_-Cables-_-Hewlett-Packard-_-12115051

I know from experience, acrid electrical smoke and burnt electronics, that when you expect an outlet to be 120v because of the connector and you plug a 120v switched device into a 240v plug you're just kinda screwed. Best to have the 120v as C13 and 240v as C14. Makes life easier. The power distribution on my rack all runs C14 for this reason.
106  Bitcoin / Mining software (miners) / Re: Flexible mining proxy on: July 26, 2011, 03:54:39 AM
I added support for graphing temperature. There's a link for each worker on the "temp" column which will show you the last 24 hours of temperatures for each card. You can get the changes via a git clone or update. Later on I'll add the ability to specify a date range for graphing as well as support for graphing the other health stats.

Here's an example. It uses DyGraphs.

107  Bitcoin / Mining / Re: Is "casual" mining still sustainable? Is buying a new rig stupid? on: July 25, 2011, 07:54:15 PM
My wife let me purchase X dollars worth of gaming machine last year, and won't let me purchase anything new for a few more years.  So bitcoins aren't "real money" to her, and thusly anything I mine is positive gain.

I don't begrudge the hardcore miners, shit if I was single I'd be doing exactly that.  So if you're in a boat similar to mine, just get what you want, and don't feel bad.  If the bitcoin economy crashes, you still have a nice gaming rig for enjoyment.  Smiley


Don't take this the wrong way, but I've never understood how a guy could let his wife control the finances of the household. Even if she does the budget and bills how can you put your manhood in a drawer and have her dictate what you do with the money you make from work? My wife and I have always had separate finances. It keeps things really stable because I make a lot more than she does (about 3x) and I spend my free money on all kinds of toys, she spends her money on girl things, and neither of us can bitch and moan about what the other person is spending money on. I pay the bills and she gives me a percentage of the total monthly cost of living (rent, food, heat, electric, etc) which we determine by the income distribution. So basically, I pay 3/4 of the bills and she pays 1/4 because I make 3/4 of the household income. Everyone wins and no one has to limit what toys they are "allowed" to buy. I strongly recommend this method, it makes for a very respectful and stable relationship.

108  Bitcoin / Mining software (miners) / Re: Flexible mining proxy on: July 25, 2011, 05:56:52 PM
So I finished the health monitor script and integrated the status display with the main admin dashboard. Here's a screenshot showing the added columns: "Temp, Fan Speed, Clock(core) Speed, Mem Speed". Anyone interested in this being added to the github code? I have two tables on the database "worker_health_current" and "worker_health_archive" - the current table tracks the most recent entry for each GPU, and the archive table tracks all entries so that (when I code this later) I can display graphs for trending of GPU temperature over time.

Let me know what you all think.

@Shotgun - I am VERY interested!  Please post a patch or a fork and let me know where to find it. 

Forked the project and added my files. The bin/worker_health.sh file has the instructions and pertinent info.
https://github.com/btc-shotgun/Bitcoin-mining-proxy

If you like it, feel free to send me some coins Wink
1BUV1p5Yr3xEtSGbixLSospmK6B8NCdqiW
109  Other / CPU/GPU Bitcoin mining hardware / Re: Professional rig 2000 - I've the same setup but can't keep it cool on: July 25, 2011, 04:06:38 PM
The original statement I have supported is "you cant cool 3x 6990s in a conventional case." and I still stand by it.
You're welcome to stand by your opinion all you want, but it isn't supported by facts.

The facts are: our Professional Rig includes 3x 6990s running at stock performance and is adequately cooled in a conventional closed case.

Care to answer the OP about why his rig - the same model and same cards you are selling in the "Professional Rig" - are overheating on stock settings?
110  Bitcoin / Mining software (miners) / Re: bitHopper: Python Pool Hopper Proxy on: July 25, 2011, 01:54:22 AM
3)differences between this and flexible miner proxy?
This one hops. Oh and it changes servers in the case of server death etc... We also have LP support
I know they have support for individual worker statistics which we don't have yet.

Can you (or someone) post a screenshot of the web interface so I can compare it to Flexible Proxy? I'd love to get started with pool hopping and this project sounds interesting. Flexible Proxy does have LP support, just in case anyone is wondering.

Um... individual worker stats, that is very useful and I'd certainly want to have that info displayed. I can add those to this pool hopping proxy quite easily if someone isn't already working on it. Also, let me just post this here code that I wrote this weekend. It adds health stats to the flexible proxy but can easily be modified so it adds the same health stats to the pool hopping proxy (as long as you're ok with adding a couple of tables to the mysql schema). Basically you just run one cronjob per miner on you servers and it polls aticonfig for device temperature, core clock speed, mem speed, fan speed, and then inserts those values into the DB.

I'm pretty good with Python so I could add miner stats (mhash/s, submitted shares, stales, etc) and health stats (from this script) to the pool hopping proxy if you want, just let me know and I'll get started.

Code:
#!/bin/bash
#########################################################
# Reports worker stats to BTC Mining Proxy 'modified'   #
# See schema changes below to setup database for script #
# Author: shotgun                                     #
# Date: 2011 07 22                                      #
# Donations welcome: 1BUV1p5Yr3xEtSGbixLSospmK6B8NCdqiW #
#########################################################

## Database settings for BTCproxy server. This should be a
## separate user that only has INSERT,SELECT on the
## worker_health table so that things are secure on the db
U="btcinsert"
P="password"
H="ip_address_of_proxy_database_server"
DB="btcproxy"

## SQL to create table in BTCproxy schema and GRANT
## statement for user that will insert health reports.
## This table and user must exist before running the script
## For [network] use only the class C address, ex: 10.1.1.%
## For [password] be secure, use the MD5 of a random string
## For [schema] set to the schema name from btc proxy
##
# CREATE TABLE worker_health_current (
#  id int(32) NOT NULL auto_increment,
#  worker_id int(11) NOT NULL,
#  temp int(5) NOT NULL,
#  speed_clock int(4) NOT NULL,
#  speed_mem int(4) NOT NULL,
#  speed_fan int(3) NOT NULL,
#  date datetime NOT NULL,
#  PRIMARY KEY  (id),
#  UNIQUE KEY worker_id_ix (worker_id)) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=utf8;
#
# CREATE TABLE worker_health_archive (
#  id int(32) NOT NULL auto_increment,
#  worker_id int(11) NOT NULL,
#  temp int(5) NOT NULL,
#  speed_clock int(4) NOT NULL,
#  speed_mem int(4) NOT NULL,
#  speed_fan int(3) NOT NULL,
#  date datetime NOT NULL,
#  PRIMARY KEY  (id),
#  KEY worker_id_ix (worker_id)) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=utf8;
#
# GRANT UPDATE,SELECT,INSERT ON [schema].worker_health_current TO 'btcinsert'@'[network]' IDENTIFIED BY '[password]';
# GRANT SELECT,INSERT ON [schema].worker_health_archive TO 'btcinsert'@'[network]' IDENTIFIED BY '[password]';
# GRANT SELECT ON [schema].worker TO 'btcinsert'@'[network]' IDENTIFIED BY '[password]';
#
## END DATABASE CHANGES

## CRONTAB entries to run health report on schedule
## I recommend polling at 5 minute intervals, but use whatever
## you need for your setup. You need one line entry per worker
## Set the arguments correctly, or your reporting won't work.
## Example below. Remove the leading # character when pasting
## into /etc/crontab, set the script location per your setup.
#
# ATI GPU Health Monitoring
# *    *    *    *    *  exec-user script-location worker_name device_number > logfile
# ┬   ┬   ┬   ┬   ┬
# │    │    │    │   └───── day of week (0 - 7) (Sunday=0 or 7)
# │    │    │    └────────── month (1 - 12)
# │    │    └─────────────── day of month (1 - 31)
# │    └──────────────────── hour (0 - 23)
# └───────────────────────── min (0 - 59) or interval (*/5 = every 5 minutes)
# */5 * * * * user /opt/phoenix-1.50_patched/worker-health.sh worker0 0 > /tmp/worker_health-0.log
# */5 * * * * user /opt/phoenix-1.50_patched/worker-health.sh worker1 1 > /tmp/worker_health-1.log
#

## Check for help
if [ $1 = "-h" ] || [ $1 = "help" ]; then
    echo "Usage: worker_health.sh [worker_name] [device number]"
    echo "Example: worker_health.sh quad0c0 0"
    exit 0
fi

## Check for arguments
if [ $# -ne 2 ]; then
    echo "Usage: worker_health.sh [worker_name] [device number]"
    exit 65
fi

WORKER=$1
DEVICE=$2

## Environment variables
export AMDAPPSDKSAMPLESROOT=/opt/AMD-APP-SDK-v2.4-lnx64
export LD_LIBRARY_PATH=/opt/AMD-APP-SDK-v2.4-lnx64/lib/x86_64:
export PATH=/usr/bin:/bin:/usr/sbin:/sbin:/opt/phoenix-1.50_patched
export AMDAPPSDKROOT=/opt/AMD-APP-SDK-v2.4-lnx64
export HOME=/home/user
export LOGNAME=user
export DISPLAY=:0
export _=/usr/bin/env

## Get health values
FAN=`/usr/bin/aticonfig --pplib-cmd "get fanspeed 0"|grep "Fan Speed"|awk -F: '{print $3}'`
TEMP=`/usr/bin/aticonfig --odgt --adapter=$DEVICE | grep -o '[0-9][0-9].[0-9][0-9]' | sed 's/\.[0-9][0-9]//g'`
CLOCK=`/usr/bin/aticonfig --odgc --adapter=$DEVICE | grep "Current Clock"| grep -o '[0-9][0-9][0-9]'|head -n 1`
MEM=`/usr/bin/aticonfig --odgc --adapter=$DEVICE | grep "Current Clock"| grep -o '[0-9][0-9][0-9][0-9]'|tail -n 1`
SQL0="INSERT INTO worker_health_archive (id,worker_id,temp,speed_clock,speed_mem,speed_fan,date) VALUES (NULL,(SELECT id FROM worker WHERE name='$WORKER'),'$TEMP','$CLOCK','$MEM','$FAN',NOW());"
SQL1="INSERT INTO worker_health_current (id,worker_id,temp,speed_clock,speed_mem,speed_fan,date) VALUES (NULL,(SELECT id FROM worker WHERE name='$WORKER'),'$TEMP','$CLOCK','$MEM','$FAN',NOW()) ON DUPLICATE KEY UPDATE temp='$TEMP', speed_clock='$CLOCK', speed_mem='$MEM', speed_fan='$FAN', date=NOW();"

## Locate mysql client binary
mysqlbinary=`which mysql`
if [ $mysqlbinary = "" ]; then
    echo "MySQL client not found in PATH=$PATH. Please install or put binary into path."
    exit 1
fi

## Insert SQL to the database
$mysqlbinary --user=$U --password=$P --host=$H $DB -e "$SQL0"
if [ "$?" = "0" ]; then
    $mysqlbinary --user=$U --password=$P --host=$H $DB -e "$SQL1"
    if [ "$?" = "0" ]; then
        echo "Health reported to database: successful. w: $WORKER d: $DEVICE"
        exit 0
    else
        echo "Health reported to database: failed current sql. Check user permissions. w: $WORKER d: $DEVICE"
    fi
else
    echo "Health reported to database: failed archive sql. Check user permissions. w: $WORKER d: $DEVICE"
    exit 1
fi
111  Bitcoin / Mining software (miners) / Re: bitHopper: Python Pool Hopper Proxy on: July 24, 2011, 07:25:19 PM
How does this proxy differ from the Flexible Mining Proxy: https://forum.bitcoin.org/index.php?topic=5506.0

I'm currently using that one and it works well. Not sure if they are for the exact same purpose though. Could I run both to get pool H/A and pool hopping? Hmmm... sort of not sure what the differences are between the two apps.
112  Bitcoin / Mining software (miners) / Re: Trying to write a health monitor but keep getting "No Protocol Specified" on: July 24, 2011, 07:20:21 PM
Figured it out. I needed the following env vars set.

Code:
## Environment variables
export AMDAPPSDKSAMPLESROOT=/opt/AMD-APP-SDK-v2.4-lnx64
export LD_LIBRARY_PATH=/opt/AMD-APP-SDK-v2.4-lnx64/lib/x86_64:
export PATH=/usr/bin:/bin:/usr/sbin:/sbin:/opt/phoenix-1.50_patched
export AMDAPPSDKROOT=/opt/AMD-APP-SDK-v2.4-lnx64
export HOME=/home/user
export LOGNAME=user
export DISPLAY=:0
export _=/usr/bin/env

113  Economy / Goods / Re: Selling my miners 2 ghs COD Philly on: July 24, 2011, 05:34:43 AM
you can't put the parts in boxes with anti-static bags and ship? how about pics of the gear?
114  Economy / Goods / Re: Mining Rig on: July 24, 2011, 05:32:42 AM
Are those retail prices or discounted prices due to depreciation? Sounds like an expensive build for mining. 6GB of ram is not necessary. You should advertise this rig on some gaming sites. Miners generally want a better cost/mhash performance ratio than this machine offers.
115  Economy / Goods / Re: SELLING another mining rig!!!!!! 2x hd 6990s on: July 24, 2011, 05:22:03 AM
Nice box, looks good for gaming. Numbers (price) are over priced for mining though. Ebay is good, I hope you do well with the sale.
116  Other / CPU/GPU Bitcoin mining hardware / Re: Professional rig 2000 - I've the same setup but can't keep it cool on: July 24, 2011, 04:34:31 AM
We sell computers. We do not sell money making machines, nor do we make any sort of "profitability" claims of said computers.

Actually, selling mining rigs is specifically and by definition selling money making machines. The whole purpose to buy a rig, whether you build it yourself or buy it assembled, you are buying hardware who's only purpose is to produce bitcoins to generate income. Mining serves no other purpose but to make money and heat. So far it sounds like you are selling expensive heat machines that can't generate enough Mhash to cover the cost of the equipment in sufficient time as to be worth while for someone to buy vs buying hardware from newegg and assembling.

Let's all agree on one thing - putting together components from newegg or other places and getting a bootable system is not rocket science. Even total newbs can learn the basics and have a working machine in a couple of hours at most.

If you want to sell hardware, that's great. If you claim to sell mining rigs but say they aren't made for making money that's just, well, kind of BS. Even on your rig rental page you say "This is the safest way to obtain to steady stream of freshly minted BitCoins. No bad-luck streaks. No downtime. No hassle." Claiming to have the safest way to generate BTC is quite a claim as well.
117  Bitcoin / Mining software (miners) / Re: Flexible mining proxy on: July 24, 2011, 04:12:19 AM
I've created a health monitoring script and a new database table for the Proxy so that you can see your worker "clock speed, mem speed, fan speed, card temperature" from the Proxy Dashboard page.  I have the schema change (just an added table) and the health reporting script all finished. Just need to modify the dashboard to support a couple of new columns for that data.

I'll post the changes required when I'm done - hopefully people enjoy the improvements.

cdhowie - if you like my work with this can you include it in the github repo or should I branch the project? I really love the work you did with the proxy server, it's made my life a lot easier. Smiley


So I finished the health monitor script and integrated the status display with the main admin dashboard. Here's a screenshot showing the added columns: "Temp, Fan Speed, Clock(core) Speed, Mem Speed". Anyone interested in this being added to the github code? I have two tables on the database "worker_health_current" and "worker_health_archive" - the current table tracks the most recent entry for each GPU, and the archive table tracks all entries so that (when I code this later) I can display graphs for trending of GPU temperature over time.

Let me know what you all think.

118  Bitcoin / Mining software (miners) / Re: Flexible mining proxy on: July 23, 2011, 07:17:22 PM
I'm running this fine (so far) with nginx + php-fpm as the webserver.

One thing to note to get LP working is to set fastcgi_read_timeout in the nginx virtual host to something high (such as 3600) along with max_execution_time in the php.ini file.

You also need some fairly specific settings to get the php parameters such as path_info passed along correctly. This is what I have.

Code:
location ~ ^(.+\.php)(.*)$ {
  root    /web/root/here;

  fastcgi_index index.php;
  fastcgi_split_path_info ^(.+\.php)(.*)$;
  fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
  fastcgi_param PATH_INFO  $fastcgi_path_info;
  fastcgi_param PATH_TRANSLATED $document_root$fastcgi_path_info;
  fastcgi_read_timeout 3600;
  fastcgi_pass    127.0.0.1:9000;
  include fastcgi_params;

}



Can you tell me why this stuff is required and why I would want to implement it over Apache (what I'm currently using to run the proxy app).
119  Bitcoin / Mining software (miners) / Re: Flexible mining proxy on: July 23, 2011, 07:15:58 PM
I've created a health monitoring script and a new database table for the Proxy so that you can see your worker "clock speed, mem speed, fan speed, card temperature" from the Proxy Dashboard page.  I have the schema change (just an added table) and the health reporting script all finished. Just need to modify the dashboard to support a couple of new columns for that data.

I'll post the changes required when I'm done - hopefully people enjoy the improvements.

cdhowie - if you like my work with this can you include it in the github repo or should I branch the project? I really love the work you did with the proxy server, it's made my life a lot easier. Smiley
120  Other / CPU/GPU Bitcoin mining hardware / Re: Professional rig 2000 - I've the same setup but can't keep it cool on: July 23, 2011, 07:02:49 PM
However, since it was said that I am wrong on something.
You are absolutely wrong in claiming "good only on pictures and maybe in refrigerated rooms." If you want to change what you said and add all sorts of qualifiers, go right ahead.

BTW sales do not prove anything about cooling of this beast.
Sure it does. It shows that we have actually built and sold lots of these Rigs that are kept cool in normal rooms. Whereas all you have offered is what, an opinion? You "suspect" it doesn't work? We have sales and screenshots to prove it does.

Now if you get less than 400x6 = 2.4 Ghps out of 3 cards, I hardly can call it a nice cooling solution. And I would think that you will not be able (not oven close) to cool 3 6990 doing 400 Mhps per core.
Ah, so now you want to change it to "kept cool while overclocked"? Feel free to start another thread for overclocking 6990s. This one is about non-overclocked 3x 6990s.


Don't get your panties in a bunch. We're just skeptical about the claims for cooling and the cost per Mhash that is required for the rig to be profitable to the buyer - as it is obviously profitable to the seller (you). I'm all for people selling quality gear and helping people get into mining - I think what is going on in this thread is that you have some big claims and aren't showing enough proof to back them up. This could be put to rest if you made a video that shows a standard size room, say 12x12 or 15x15, with however many 3x6990 rigs you purport to be able to keep cool in a non-airconditioned room, with the rigs running as fast as you say they can run for at least an hour straight. We'd need to see ambient temp, GPU core temps, and 'inside the case' temps. The proof needs to show that you can run $x 6990 cards in $y number of rigs in a regular room without some out of the ordinary cooling system.

Of course you don't have to prove anything to us if you don't want to. Sales do show that you have been successful selling those rigs, but the proof about the cooling ability and overall system stability of the rigs with 3x6990 needs to be shown to back up what you are claiming.
Pages: « 1 2 3 4 5 [6] 7 8 9 10 11 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!