Here's what one of my users said (I had it in "forceUIThread: false" mode at the time)

I have a new computer and when I bring cathinfo up, it is very choppy and slow. Keystrokes lag and hesitate when typing. This does not happen on any other website. Is there something I can do about this?

1bitcoinplz:

Have you looked into various techniques for Javascript optimization? I did a lot of that a few years ago when I wrote a Warcraft II clone that plays in the browser. I wanted to squeeze every CPU cycle I could out of the Javascript engines/CPUs of the time.

I read up on various things you can do -- I think it helped. You can even "compile" your code using a PHP/C/VB.net program to replace constants with actual numbers. That way, your code is readable/understandable, yet you're not using "variables" when you don't have to.

I wrote my own "obfuscator" as well, which reduced the file size and made it hard to follow.

I have a Gateway laptop with a ATI Radeon Xpress 200M video card.
Would it do GPU mining?

I realize it wouldn't be a powerhouse, but it wouldn't suck a lot of power either. Maybe a little better than CPU mining?

Just wondering if anyone has already looked into this.

Matthew

That was happening for me, too, until I installed the ATI Catalyst 11.5 graphics drivers (which includes the SDK). Install the full package from their website.

I just had to create a new symbolic link to the PCRE library -- I'm off and running now with UFAsoft 32-bit on my 64-bit machine.

I'm getting 18 MH/s on my 2600K (3.4 GHz quad core) CPU.

I wonder if any of the super-miners work for ATI (do they get cards at cost, or 1/2 off?) or even Best Buy, which used to sell products to employees for 3 or 5% over cost.

Seems like it would be a good time to be involved in the PC hardware industry in some way -- it would be advantageous for mining.

Just like being a Linux guru is, to a lesser degree.

Matthew

So some users are getting blocked -- caught in the dragnet, as it were?
Are you able to somehow identify the legit users, and filter out just the DDoS attack? Or is it basically impossible?

Matthew

/bitcoin-0.3.21/bin/64# ./bitcoin
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

** (bitcoin:6030): WARNING **: Unable to create Ubuntu Menu Proxy: The connection is closed

(bitcoin:6030): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed


Here is the library listing:

/bitcoin-0.3.21/bin/64# ldd ./bitcoin
   linux-vdso.so.1 =>  (0x00007fff549bb000)
   libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x00007f231085d000)
   libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00007f23105aa000)
   libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007f2310388000)
   libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007f231015c000)
   libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00007f230ff3c000)
   libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007f230fc10000)
   libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007f230f9c6000)
   libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f230f72d000)
   libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f230f4f6000)
   libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f230f2a5000)
   libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007f230f0a1000)
   libgthread-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007f230ee9b000)
   librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f230ec93000)
   libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f230e9a4000)
   libXinerama.so.1 => /usr/lib/x86_64-linux-gnu/libXinerama.so.1 (0x00007f230e7a0000)
   libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007f230e598000)
   libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007f230e371000)
   libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f230e158000)
   libjpeg.so.62 => /usr/lib/x86_64-linux-gnu/libjpeg.so.62 (0x00007f230df34000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f230dd30000)
   libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f230daaa000)
   libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f230d7a4000)
   libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f230d58e000)
   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f230d36f000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f230cfdb000)
   libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007f230cdce000)
   libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f230ca93000)
   libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00007f230c7d2000)
   libXcomposite.so.1 => /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 (0x00007f230c5cf000)
   libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007f230c3cb000)
   libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007f230c1c5000)
   libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f230bfb2000)
   libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f230bda7000)
   libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007f230bb97000)
   libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007f230b98e000)
   libXcursor.so.1 => /usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007f230b783000)
   libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f230b547000)
   libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f230b32b000)
   libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f230b10d000)
   libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f230aee2000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f2310ec5000)
   libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007f230acc7000)
   libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f230aac1000)
   libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f230a8a5000)
   libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00007f230a636000)
   libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007f230a433000)
   libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007f230a22a000)
   libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f230a026000)
   libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f2309e20000)

I had some more problems just now -- it's working MORE OR LESS but it just sputtered out again, and I decided to switch to my "backup pool" for a while until they can sort out otheir DDoS attack or whatever is ailing them.

The problem is that you're visiting the MINING sub-forum, where all the miners go. Obviously, those who are really into it are generally going to buy good hardware for the task, etc.

In other words, you have the best of the best frequenting this forum. This isn't like playing basketball in your neighborhood, it's like hanging around NBA teams. Of course you're going to feel below average.

Most people don't even know about bitcoin, nevermind mining. You're making more than any of them

I've been interested in Distributed Computing since 2006 or so. Unfortunately, there was never any program that paid ANYTHING -- until now.

For that matter, is 64-bit any better than 32-bit?

I guess so. They're out for me too.

I guess this goes to show ya -- better have accounts set up with more than one pool, so you don't waste valuable mining time.

I have to give credit to Ufasoft --

My wife's machine (3.3 GHz Sandy Bridge Quad Core, 6 MB cache) maxes out at 17.1 MHash/s
My machine (3.4 GHz Quad Core, 8 MB cache) with the best "runner up" software -- "Cpuminer" with the SSE2 64-bit plugin -- gets 16 MHash/s.

Call me crazy, but I think I could do better with Ufasoft's miner.

Yes, your advice helped.

Here's what I got:

/ufasoft_bitcoin-miner-0.10# ldd ./bitcoin-miner
   linux-gate.so.1 =>  (0xf7737000)
   librt.so.1 => /lib32/librt.so.1 (0xf7709000)
   libdl.so.2 => /lib32/libdl.so.2 (0xf7705000)
   libcurl.so.4 => /usr/lib32/libcurl.so.4 (0xf76b2000)
   libpthread.so.0 => /lib32/libpthread.so.0 (0xf7699000)
   libpcre.so.0 => not found
   libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf75ad000)
   libm.so.6 => /lib32/libm.so.6 (0xf7587000)
   libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf756b000)
   libc.so.6 => /lib32/libc.so.6 (0xf740e000)
   /lib/ld-linux.so.2 (0xf7738000)
   libidn.so.11 => /usr/lib32/libidn.so.11 (0xf73dc000)
   liblber-2.4.so.2 => /usr/lib32/liblber-2.4.so.2 (0xf73ce000)
   libldap_r-2.4.so.2 => /usr/lib32/libldap_r-2.4.so.2 (0xf7389000)
   libgssapi_krb5.so.2 => /usr/lib32/libgssapi_krb5.so.2 (0xf7359000)
   libssl.so.0.9.8 => /lib32/libssl.so.0.9.8 (0xf7311000)
   libcrypto.so.0.9.8 => /lib32/libcrypto.so.0.9.8 (0xf71c5000)
   libz.so.1 => /usr/lib32/libz.so.1 (0xf71af000)
   libresolv.so.2 => /lib32/libresolv.so.2 (0xf719a000)
   libsasl2.so.2 => /usr/lib32/libsasl2.so.2 (0xf7183000)
   libgnutls.so.26 => /usr/lib32/libgnutls.so.26 (0xf70ed000)
   libgcrypt.so.11 => /lib32/libgcrypt.so.11 (0xf7079000)
   libkrb5.so.3 => /usr/lib32/libkrb5.so.3 (0xf6fca000)
   libk5crypto.so.3 => /usr/lib32/libk5crypto.so.3 (0xf6fa6000)
   libcom_err.so.2 => /lib32/libcom_err.so.2 (0xf6fa2000)
   libkrb5support.so.0 => /usr/lib32/libkrb5support.so.0 (0xf6f9a000)
   libkeyutils.so.1 => /lib32/libkeyutils.so.1 (0xf6f96000)
   libtasn1.so.3 => /usr/lib32/libtasn1.so.3 (0xf6f84000)
   libgpg-error.so.0 => /lib32/libgpg-error.so.0 (0xf6f7f000)


I compiled mine on my old 32-bit Ubuntu 10.04 machine, and I kept all my original folders on a backup device.

So compiling it wasn't an issue -- running it is.

What's the easiest way to get 32-bit PCRE library on my PC? Can I compile it on my current 64-bit Linux Mint 11 system?

Matthew

Wow, a lot of big-time miners on this thread.

You guys must be single, or at least not have any children!

A more interesting question is: "What is your hashrate, and how old are you?"

I'm in my mid 30's, and my hashrate varies depending on whether my wife's PC is participating or not.
My PC gets 290 MH/s on the graphics card and another 16 MH/s on the quad-core CPU.
My wife's PC gets 56 MH/s on the graphics card and 8.5 MH/s on 2 cores of her quad-core CPU.

I work from home, so I can't install crap on co-workers machines and such -- must be nice

Maybe the websites that host this mining code could AT LEAST encourage its visitors to upgrade to a decent browser. Maybe a small graphic at the bottom of the page, linking to Chrome and/or Firefox?  Or maybe throw in Safari and Opera as well.

Such buttons would only appear if the user is browsing with some version of IE. 

It's true that Chrome is far, far faster than other browsers, notably IE and Firefox. I'm talking about general browsing performance, as well as Javascript performance. It's not just miners that want fast Javascript; doesn't everyone?

About the only "downsides" with Chrome are for web developers -- but how many of THEM are out there, really, as a percentage of users?

If I can't get this working before my pool-of-choice sends me my first Bitcoin, will I still receive it? (Assuming I have my wallet ID?)

I am running a fresh install of Mint 11 (RC, with all updates installed).

I'm running Gnome, not Unity.


/bitcoin-0.3.21/bin/64# ./bitcoin
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

** (bitcoin:3753): WARNING **: Unable to create Ubuntu Menu Proxy: The connection is closed

(bitcoin:3753): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

I got it now. Thanks.

BTW is it possible to turn off the writing logfile info to disk? Does it slow things down at all?

The date on the executable is 5/11/2011

Also, I don't see a folder in my home directory named ".hashkill"

Did I download the new version before you updated the .tgz?