Posts by Rabinovitch
log in
1) Message boards : Number crunching : Linux ( ubuntu 10.10 64 bit) twice slower then Win (Message 12718)
Posted 2324 days ago by Rabinovitch
So what caused such a slow processing? The same GPU should perform same computation (using the same technology, OpenCL) in the same period of time... Is it caused by such an underdone OS itself which *buntu is?
2) Message boards : Number crunching : GPU Missing (Message 6329)
Posted 2890 days ago by Rabinovitch
Well, how about openSUSe 11.2? Didn't found any way to make BOINC to detect a "usable GPU" on it...

Please somebody describe a way of BOINC installation on newly installed system (exactly openSUSE 11.2 x64, exactly the way allowing to use CUDA)!
3) Message boards : Number crunching : Linux 64 bits GPU time (Message 3936)
Posted 2983 days ago by Rabinovitch
Try this one to see if anything changes -> http://calbe.dw70.de/collatz/collatz_2.02_x86_64-pc-linux-gnu__cuda22.tar.bz2

Warning: the version number changed in that one to 2.02!


Many thanx! It works for me too! Without any other changes (no_priority_change was set earlier)!

Now WU processing time is about 50-70 minutes (instead of 3-4 hr before).
4) Message boards : Number crunching : Linux CUDA Application Installation (Message 3933)
Posted 2983 days ago by Rabinovitch
God...

Downloaded now several WUs of Milkyway@home for Linux. Everything was downloaded without my participation, no any links I was forced to do (for it's libcudart_64bit_23.so) - it just started to work... The same WU processing speed as under Windows 7 x64, the same GPU utilization (at least the same GPU temperature :-))...

Why don't Collatz' developers ask Milky's developers for an advice, how does they made their project so "user-friendly"? :-)))
5) Message boards : Number crunching : Linux CUDA Application Installation (Message 3704)
Posted 2991 days ago by Rabinovitch
Well, for me this message was very useful. Try it.

2 all: guys. I don't know what to do. On the same machine and in the same conditions one WU is processing normally, and next one - 5 times slower.

My cc_config:


<cc_config>

<options>
<no_priority_change>1</no_priority_change>
</options>

<log_flags>
<task>1</task>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<cpu_sched>0</cpu_sched>
<cpu_sched_debug>0</cpu_sched_debug>
<rr_simulation>0</rr_simulation>
<debt_debug>0</debt_debug>
<task_debug>0</task_debug>
<work_fetch_debug>0</work_fetch_debug>
<unparsed_xml>0</unparsed_xml>
<state_debug>0</state_debug>
<file_xfer_debug>0</file_xfer_debug>
<sched_op_debug>0</sched_op_debug>
<http_debug>0</http_debug>
<proxy_debug>0</proxy_debug>
<time_debug>0</time_debug>
<http_xfer_debug>0</http_xfer_debug>
<benchmark_debug>0</benchmark_debug>
<poll_debug>0</poll_debug>
<guirpc_debug>0</guirpc_debug>
<scrsave_debug>0</scrsave_debug>
<app_msg_send>0</app_msg_send>
<app_msg_receive>0</app_msg_receive>
<mem_usage_debug>0</mem_usage_debug>
<network_status_debug>0</network_status_debug>
<checkpoint_debug>0</checkpoint_debug>
</log_flags>
</cc_config>
6) Message boards : Number crunching : Linux CUDA Application Installation (Message 3674)
Posted 2992 days ago by Rabinovitch
First of all, try to upgrade BOINC to the latest version from BOINC site. PN me if you need to upgrade manually BOINC client that was installed from the repository. It's easy. ;-)

Then we well try to make Collatz work on your machine.
7) Message boards : Number crunching : Linux CUDA Application Installation (Message 3649)
Posted 2993 days ago by Rabinovitch

However, since you're running ubuntu, you need to create a file called cc_config.xml in your boinc directory and add the following content to it:


<cc_config>
<options>
<no_priority_change>1</no_priority_change>
</options>
</cc_config>



Could you please get more specific information - where it should be placed to? May be to the usr/bin directory, where boinc executables are placed? Or to the
var/lib/boinc-client, boinc's data directory (or to the project's directory)?
8) Message boards : Number crunching : Linux CUDA Application Installation (Message 3630)
Posted 2994 days ago by Rabinovitch
Thanx to all in this thread - finally it works!

p.s. what is usual time for WU processing on GTX260?
9) Message boards : Number crunching : Linux CUDA Application Installation (Message 3242)
Posted 3008 days ago by Rabinovitch
May be it's a nice idea to publish a kind of HOWTO for Linux x64 app installation, as far as we forced to do it by hands? 'Cause I got a SIGSEGV: segmentation violation too, and I am not so experienced Linux user to quickly understand what to do without advices... Please someone help me to continue crunching one of my lovely projects!

p.s. for example, ldd shows:

rabinovitch@beast-machine:/var/lib/boinc-client/projects/boinc.thesonntags.com_collatz$ ldd collatz_2.01_x86_64-pc-linux-gnu__cuda22
linux-vdso.so.1 => (0x00007fff565df000)
libcuda.so.1 => /usr/lib/libcuda.so.1 (0x00007f3ef05c3000)
libcudart.so.2 => /usr/lib/libcudart.so.2 (0x00007f3ef0384000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f3ef0074000)
libm.so.6 => /lib/libm.so.6 (0x00007f3eefdf0000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007f3eefbd9000)
libc.so.6 => /lib/libc.so.6 (0x00007f3eef86a000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f3eef64e000)
libz.so.1 => /lib/libz.so.1 (0x00007f3eef437000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f3eef233000)
librt.so.1 => /lib/librt.so.1 (0x00007f3eef02b000)
/lib64/ld-linux-x86-64.so.2 (0x00007f3ef0a5f000)
rabinovitch@beast-machine:/var/lib/boinc-client/projects/boinc.thesonntags.com_collatz$

Seems that I need to obtain "linux-vdso.so.1", but where from?
10) Message boards : Number crunching : 128 bit windows 7 & 8! (Message 2984)
Posted 3018 days ago by Rabinovitch

Question is, we have'nt seen any significant performance increase between 32 and 64 bit code, and, the world is still at 32 bit and 64 is'nt wide spread, so 128 bits should be a wait and see, like Nvidias next GPU. :P


"We"? Who's those "we" are?

x64 is (!) useful, but not for all tasks may be, and keep in mind that some of programmers are lasy enough to optimize their code for x64 and debug it. Remember, that long time ago multicore CPUs were slower than single-core ones - the case was the same - lack of optimization for parallel data processing. So without changes in code and compiling it wi wil no get any benefits even of 256-bit CPUs.

p.s. note that D-Wave company is researching now exactly new algorithms for quantum computers - they understand, what is the MOST important to get a max from quantum computing.
11) Message boards : Number crunching : 2.06 + 6.10.13 = CPU work even though set to no? (Message 2941)
Posted 3020 days ago by Rabinovitch
Got 6.10.11. Suddenly it started to receive CPU Wus instead of checkbox in the project's preferences saying not to do so. When it will be fixed?
12) Message boards : Number crunching : 191.03 new beta-driver for NVIDIA (Message 2365)
Posted 3036 days ago by Rabinovitch
The v191.03 still doesn't fix the problem of the NVIDIA Cards Down Clocking at GPU Grid, I tried it last night on 1 Box and had 1 Card Down Clock Twice within an hour.

Strange to hear again about this problem. On GPUGRID's forum there was a discussion how to solve this.

There is a simple way to win this phenomena using RivaTuner, even with new driver. If you can't find this thread please PM me.
13) Message boards : Number crunching : 191.03 new beta-driver for NVIDIA (Message 2364)
Posted 3036 days ago by Rabinovitch
Evrth. is OK with the project with this beta driver. But seems like it not OK in the games (exactly in Titan Quest and King's Bounty).
14) Message boards : Number crunching : 191.03 new beta-driver for NVIDIA (Message 2112)
Posted 3039 days ago by Rabinovitch
Have installed it yesterday. Collatz processing well.
15) Message boards : Number crunching : Collatz v2.0 Status (Message 1383)
Posted 3049 days ago by Rabinovitch
So what's new in 2.0 apps (besides CUDA 2.3 SDK, certainly...)? Which benefits it gives to number crunching?

p.s. can I increase load of nVidia GTX260 by the way [url-http://boinc.thesonntags.com/collatz/forum_thread.php?id=68&nowrap=true#1361]described[/url] below?
16) Message boards : Number crunching : Collatz v2.0 Status (Message 1254)
Posted 3050 days ago by Rabinovitch
Evrth. seems OK. But BM could receive 2.0 tasks only after resetting project somewhy...

BTW, is it OK that time per WU became only one (!) minute instead of appr. 30 minutes before 2.0?

Win 7 x64, 190.38...
17) Message boards : Science : Founded numbers (Message 734)
Posted 3071 days ago by Rabinovitch
Please post here newly finded numbers - it is very important for crunchers to see the concrete project's results...
18) Message boards : Number crunching : Long crunchtime? (Message 713)
Posted 3073 days ago by Rabinovitch
I'm using 190.38 drivers on a GTX260 without any problems...;)


So am I. 8-)
19) Message boards : Number crunching : CUDA only work. (Message 553)
Posted 3085 days ago by Rabinovitch
My great ask to project developers is to make at last possible run only cuda Wus, like in SETI. Then I could run cuda Wus constantly on my GTX260, without any magig with enable/disable CPU Wus... Is it so difficult?
20) Message boards : Number crunching : ATI/CAL enabled Boinc client (Message 448)
Posted 3091 days ago by Rabinovitch
Ohh, so I'm not alone with my problem.

Just attached my home machine (Win7U x64, BM 6.6.37, nVidia driver 190.38), got the next messages:

08.08.2009 8:07:05 Collatz Conjecture Sending scheduler request: Project initialization.
08.08.2009 8:07:05 Collatz Conjecture Requesting new tasks for CPU and GPU
08.08.2009 8:07:10 Collatz Conjecture Scheduler request completed: got 0 new tasks
08.08.2009 8:07:10 Collatz Conjecture Message from server: No work sent
08.08.2009 8:07:10 Collatz Conjecture Message from server: Can't use CAL app for collatz: Your computer has no CAL device




Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.