Welcome to MilkyWay@home

Posts by Crunch3r

1) Message boards : News : Release of MilkyWay Sepearation Modified Fit v1.30 (Message 61561)
Posted 20 Apr 2014 by ProfileCrunch3r
Post:
Hey guys,

Currently, there is an issue getting the boinc libraries to compile with our code in the win32 version. I had a pretty sketchy fix to it over last summer, but in the end it ended up not working on all computers.

Thank you,

Jake W.


Could you be more specific about that?

I've got no problem compiling it for 32 bit nor 64 bit at all.
I'm guessing that you think you need to compile/link to the latest boinc api/lib while compiling a new MW app, which is not needed at all. Use the one the previously worked...

2) Message boards : News : Release of MilkyWay Sepearation Modified Fit v1.30 (Message 61549)
Posted 19 Apr 2014 by ProfileCrunch3r
Post:
Hey guys,

This release does not fix the win32 issues, I'm sorry. It should be possible for you guys to compile your own version of milkyway@home for win32 if you are interested. The issue with us releasing a version is it has to work with all computers running win32 even with some outdated hardware, which has proven itself to be very difficult. If you can get it running on your machine though it is possible to still get work units and run them for credits.

Jake W.


Howdy,

I'm not sure what that win32 "bug" is all about but with some clarification about it, i might be able to help...
3) Message boards : Application Code Discussion : Why are the MW sep. mod. fit 1.28 x86 (32 bit) apps not listed in the apps list? (Message 61548)
Posted 19 Apr 2014 by ProfileCrunch3r
Post:
Is this about the CPU or the GPU app ?

4) Message boards : Number crunching : GPU missing since upgraded nvidia drivers (Message 61547)
Posted 19 Apr 2014 by ProfileCrunch3r
Post:
GPU missing since I upgraded nvidia drivers to 335.23 release date 3/10/2014

I suppose when MW@Home updates they will re-appear?



First of all, it's NOT milkyways fault(despite the utter nonsense mikey posted). It's boinc that's not detecting your GPU in the first place, so milkyway doesn't know about it at all.

So either upgrade you boinc client to some buggy alpha version or downgrade the driver to the one that worked preiviously.
5) Message boards : Number crunching : Using SSE2 path... (Message 52625)
Posted 23 Jan 2012 by ProfileCrunch3r
Post:
Any ideas on why is this computer using SSE2 instead of SSE3 for the GPU app? The CPU is SSE3 capable, runs the SSE3_AMD optimized SETI app and I'm using the current stable version of BOINC (6.12.34) and as I have seen on other hosts using that version, they are using SSE3, so should be new enough.


I wouldn't bother much about that. There's no use for SSE3 instructions while calculating the "likelihood". (takes only a few sec...)

And since you're running the app on a AMD CPU, it's highly likely that SSE3 code will be quite a bit slower after all.

FWIW, i'm running a custom 0.91 app here on a AMD X2 5200+ that uses the SSE3 code path (ICC 12.x.x, avg 3.02 sec/likelihood/calc. )and it's slower than your AMD X2 5600+ using the stock app (2.4 sec.). ;)
6) Message boards : Number crunching : Suddenly most results invalid (Message 51528)
Posted 27 Oct 2011 by ProfileCrunch3r
Post:
Whenever I check out validate errors, more than 95+% of the time it's because the result is missing. The workunit succeeded and everything, but the result is simply not in the output. We get results back from the stderr for quite a while (this wasn't true about a year ago), and I don't many other projects do this.

There are two issues (at least one is with BOINC) which I'm aware of which results in this. First, there seems to be an arbitrary cutoff where you lose part of the stderr log if it's large, but that is much less frequent.

Second, there seems to be a (more frequent) problem where sometimes for no reason some of the stderr is lost (the important part with the result). There are strange things that happen with CAL and OpenCL where stderr/stdout don't get flushed correctly on program end. I've sort of noticed this for a long time, and recently were mentioned on the AMD OpenCL forums as a AMD known issue.



FWIW, here's my opinion on the subject...

There's a major issue with results from CPU, ATI AND NVIDIA OCL apps since all of them are producing way to different results.

I've seen this happening myself where a ATI Cayman result was compared to a CUDA OCL result and those two where way to different to validate (background_likelihood and and all the stream integrals and so on), so another WU was sent out to a CPU, which also had a result that was not within the needed precision to get validated....

So the question is, which app(CUDA OCL, ATI CAYMAN, ATI CYPRESS, CPU Optimized ) does return the proper result....

I do know that the MY source code (SSE2/SSE3 hand optimized) that is being used in the new stock 0.88 CPU app (which was ported from some old V 0.18/0.20 code) did return the correct results compared to the old optimized Gipsel CPU/GPU and old stock apps.

The question is which app does give wrong results as of now... What we need is some sort of "integrated integrity check" some fixed results that are hard coded into the app code and can be tested by running "mw_client_app.exe -test" or something like that (make sure that it'll take less than 30 min on a CPU)

Besides all that, there's still the issue with using boincs "stderr" for sending back the results.... Having an empty stderr is a long known issue with boinc which goes back at least 5 years... Of course that was never a problem till MW incorporated using stderr to include the WU results as well.

Regarding that, you'd better talk to Rom Walton or DA to get that fixed once and for all.



7) Message boards : Number crunching : Lastest Stock Apps - Optimized or Not (Message 50047)
Posted 11 Jul 2011 by ProfileCrunch3r
Post:
My own machines:

Dual Quad Xeon 5365 ES (8 cores)-> SSE3 app -> http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=62008

Core i3 @ 2.13 GHz / HT enabled (4 threads) SSE4.1 app -> http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=281287
8) Message boards : Number crunching : Lastest Stock Apps - Optimized or Not (Message 50045)
Posted 10 Jul 2011 by ProfileCrunch3r
Post:
I think I know!!

They get all invalid :-(

I return to stock app.


Yes, that's why i pulled the download...(and sorry for the long time it took me to reply).. anyway with a propper solution file for MS VS without having to digg through useless cmake txt CRAP files that can't even generate proper makefiles without crashing/erroring out using the latest cmake downloads, it was just a guessing game miswsing some vital config parameters (TG Math... yeah, we got that using ICC and MW_SINCOS is computing CRAP using ICC...)...

Anyway... while digging through this unessassary cmake txt file BS... i finally got it working,linking and validating....

(if anyone want's to compile the code using a proper VS solution project (2005 or 2010)without the retarded hassle to digg through useless cmake txt files... let me know... i'll upload them to ease the pain i was ging through to get everything compiled and linked...)

So.. now that it works... we got a few new apps supporting Intel SSE4.1, Intel SSE3 and Intel/AMD SSE2 (PENTIUM4_SSE2 and AMD SSE2)

for those that know code take a look at -> http://board.mpits.net/viewtopic.php?f=32&t=77.. that one includes source code that replaces the stock 0.91 source from github (should hopefully be integratated in the next stock source code...!(Matt, that's your part :p))

Anyway...
all new optimized apps are linked, downloadable at http://www.mpits.net/opt_mw.php
(do not hotlink the zip files or modify them without permission!!!)

Optimized apps for Pentium4 (SSE2/SSE3) and AMD CPUs using AMD_SSE2 tuned ops(K8,K10) will be added tomorrow... stay tuned and look at http://www.mpits.net/opt_mw.php or http://board.mpits.net/viewtopic.php?f=32&t=77 for updates!!!

Changelog:

- NEW using GROMACS exp_pd function for SSE2 and SSE4.1(addidional 5% faster)(see code)

- NEW using _mm_fsqrt_pd (SSE approx. converting to SSE1(RCP_SRQT) and SSE2 newton raphson stuff... up to 52 bit precission) (see code)

- NEW using PENTIUM4 _mm_div_pd replacement function (see code)

- NEW, faster AMD_SSE(K8,K9,K10) _mm_div_pd replacement (see code)

JOIN BOINC United to get exclusive access to new prelelease optimized GPU & CPU apps!
9) Message boards : Number crunching : Lastest Stock Apps - Optimized or Not (Message 49600)
Posted 26 Jun 2011 by ProfileCrunch3r
Post:
When I use the app_info.xml, must there also be an entry for the N-body in it?


You don't have to run n-body at all (why isn't it possible in the user prefs to disable n-body ???).

The included app-info.xml doesn't have an entry for n-body so you're only going to run separation WUs.
10) Message boards : Number crunching : Lastest Stock Apps - Optimized or Not (Message 49595)
Posted 26 Jun 2011 by ProfileCrunch3r
Post:
Here's a 'optimized' CPU app which was compiled using the Intel(R) C++ Compiler XE 12.0.4.196 for Windows.

A SSE2 compatible CPU is required (AMD & Intel)!
Difference is that we're using Intels LibM especially the exp(e^x) function, which is faster than the 'stock' SSE2 polyn. eval....

download -> MilkyWay Separation SSE2 Intel&AMD
11) Message boards : Cafe MilkyWay : Team Recruitment III (Message 49591)
Posted 26 Jun 2011 by ProfileCrunch3r
Post:
BOINC UNITED - Let your Computer be part in scientific experiments.



BOINC UNITED is a unique, international team open to all that are interested.

Be part of something special!

Combining our knowledge, having inspirational talks with our Members and helping out the scientific community by participating in various BOINC Projects.

Please make sure to visit us at our BOINC UNITED Homepage and our BOINC UNITED Forum!

Make sure to join us here at the project to be part of something special.

We can help cure diseases, study global warming, discover pulsars, map the milkyway galaxy and do many other types of very important research that helps the scientific community.

Together we can make a difference!



Visit us at:
12) Message boards : Number crunching : GPU Requirements (Message 49578)
Posted 25 Jun 2011 by ProfileCrunch3r
Post:
... and the AMD/ATI HD cards that don't do DP (well enough):

6850
6790
6670
6570
6450

5770
5750
5670
5570
5470

4770
4670
4650
4550
4350


wrong ... the 4770 can do DP...
13) Message boards : Number crunching : Lastest Stock Apps - Optimized or Not (Message 49576)
Posted 25 Jun 2011 by ProfileCrunch3r
Post:

Just the past week a 'optimized' stock app was released. I am down to 9-10 hours on my P4 Xp for the de_separation_13_3s tasks. A large improvement over the previous app. Still seems slightly slower than the old Opti apps.


Yes, the new stock opti apps are slower. The stock app is using a dispatcher that chooses a code path (SSE level) which is supported on your CPU and the rest of the code is not optimized at all.

(The whole new build system is also preventing me from releasing some more tuned binaries using the intel compiler etc... it's a real pain in the ass and i hate that cmake crap!!)

A major part of the optimizations is still missing, hopfully Matt will find the time to integrate it into the stock app. That one will boost performance again and should outperform the old optimized cpu apps by a few percent.
14) Message boards : Number crunching : Reverting to Stock (Message 49433)
Posted 19 Jun 2011 by ProfileCrunch3r
Post:
First of all .. why do you reply to a post that's almost a year old ???

This is supposed to be science, not a race to see who can accumulate the most points.


It is science and why the hell do you think there's a system in place that counts points ??? It's a race AND it's a big part of BOINC!


Using anything other than the project approved software is BS and you're being childish and threatening the integrity of the projects. If you don't understand WHY, you don't belong here.


Actually your post is BS!... there are optimized apps out there that do SCIENCE faster than the stock apps and those apps are approved... so no need to bitch about that. Get your facts straight before posting crap like that!
15) Message boards : Number crunching : Is MW going to be a GPU project now? (Message 48635)
Posted 9 May 2011 by ProfileCrunch3r
Post:
Without using an opti app Cpu performance and credits are poor. Is there any plans to put out better cpu apps?


I know that the stock app is pretty much unusable on a CPU.
FWIW, it seems that i can reduce crunching times to less than ~5h on a XEON(5365@3 Ghz, core 2 based)...

Anyway, i do know that that's far away from what the previous opt app did...

I'd be interested to know some crunch times on different CPUs with the stock app (cpu:time:credits), before using a LUT for the INT EXP part...
(wich i know for a fact that the previous optimized CPU app used and i allready suggested to Matt for the GPU BUT it'll greatly speed up the stock CPU app as well)


Is this from using compilation flags, or changing the code?

If any of the changes are things we can do on our end, we'd be more than happy to implement them.


Code changes. I've given Matt some hand vectorized code (SSE2/SSE3) but there's still work to be done on that.
16) Message boards : Cafe MilkyWay : Team Recruitment III (Message 48619)
Posted 8 May 2011 by ProfileCrunch3r
Post:
BOINC UNITED - Let your Computer be part in scientific experiments.



BOINC UNITED is a unique, international team open to all that are interested.

Be part of something special!

Combining our knowledge, having inspirational talks with our Members and helping out the scientific community by participating in various BOINC Projects.

Please make sure to visit us at our BOINC UNITED Homepage and our BOINC UNITED Forum!

Make sure to join us here at the project to be part of something special.

We can help cure diseases, study global warming, discover pulsars, map the milkyway galaxy and do many other types of very important research that helps the scientific community.

Together we can make a difference!



Visit us at:
17) Message boards : Number crunching : Is MW going to be a GPU project now? (Message 48331)
Posted 28 Apr 2011 by ProfileCrunch3r
Post:
The next CPU release will be faster for most people


Yes, quite a bit faster than the 0.50sse2 app.

My Xeon needs ~ 8800 sec. for a 213 credit WU (13_3s_fix20)(Intel compiler). Depending on the compiler used for the stock app, it should be ~ 10k sec(or less).

Not bad for the first try.
18) Message boards : Cafe MilkyWay : Team Recruitment III (Message 48179)
Posted 24 Apr 2011 by ProfileCrunch3r
Post:
BOINC UNITED - Let your Computer be part in scientific experiments.

BOINC UNITED is a unique, international team open to all that are interested.

Be part of something special!

Combining our knowledge, having inspirational talks with our Members and helping out the scientific community by participating in various BOINC Projects.

Please make sure to visit us at our BOINC UNITED Homepage and our BOINC UNITED Forum!

Make sure to join us here at the project to be part of something special.

We can help cure diseases, study global warming, discover pulsars, map the milkyway galaxy and do many other types of very important scientific research that helps making the world a better place for all of us.

Together we can make a difference!



Visit us at:

19) Message boards : Number crunching : RCOS Spring 2011... (Message 48177)
Posted 24 Apr 2011 by ProfileCrunch3r
Post:
ing the likelihood calculation...well gipsels app did that on the CPU as well.

So even if you move it to the GPU, you're still not getting the performance of Gipsels app.. it'll still be at least 20% slower(copmpared to those,running stock without tuning gipsels app for maximum output).


And that's already using my 'opt' app that only uses 2 sec to calculate the likelihood on the cpu(vectorized sse2), compared to the 5 to 8 sec that the stock app uses on my V8 5365 xeon...
20) Message boards : Number crunching : RCOS Spring 2011... (Message 48175)
Posted 24 Apr 2011 by ProfileCrunch3r
Post:
Those are painful to watch. I'm so bad at talking.


Yeah... the audio sucks. Anyway, some of your assumtions are wrong,especially regarding that 'random' german guy called 'Gipsel'... read my PMs..
and regarding the likelihood calculation...well gipsels app did that on the CPU as well.

So even if you move it to the GPU, you're still not getting the performance of Gipsels app.. it'll still be at least 20% slower(copmpared to those,running stock without tuning gipsels app for maximum output).


Next 20

©2019 Astroinformatics Group