Posts by cenit

41) Message boards : Number crunching : No usable GPU (Message 36798) Posted 26 Feb 2010 by cenit Post: did you remember to not tick the protected mode installation? if you're unsure, uninstall boinc and reinstall without selecting that option!
42) Message boards : News : RPI Press Release (Message 36412) Posted 11 Feb 2010 by cenit Post: it's also here http://www.physorg.com/news185028222.html
43) Message boards : News : lowering purge time (Message 36306) Posted 6 Feb 2010 by cenit Post: Does this affect sending results back? Before Boinc Mgr processed pretty much my whole queue of MW Wu's, but now on all comps it seems to send&report every wu immediately. Not a big problem for me, but if this is the same for all users this should create a lot of network traffic and I/O on server? It shouldn't effect that at all. It might have been some of the other server changes. you should set a minimum interval between two connection longer, like 5 minutes, so that people with dual 5970 should still have enough work to keep those monster busy while every other cruncher will wait at least sometime before trying to report finished wu, even if they have set boinc manager "connect about every 0.00 days". This should help lower your I/O strain on the server... ps: you could even set 10 minutes (or 20, even 30!) if you make bigger WU or if you enable GPUs to download more work than CPUs (but then, we kenow that you have some database problems if you do so)
44) Message boards : Number crunching : GPU Requirements [OLD] (Message 35847) Posted 19 Jan 2010 by cenit Post: you're forgetting fabulous ATi HD 4770. edit: I'm still asking myself how ATi decided to not include DP on 57xx series... edit2: this pdf from ATi http://developer.amd.com/gpu/ATIStreamSDK/assets/ATI_Stream_SDK_Getting_Started_Guide_v2.0.pdf has all the data that you could need. Go to last page, section 4
45) Message boards : News : Patch for GPU application's CPU utilization (Message 35734) Posted 17 Jan 2010 by cenit Post: Nope, but from what I hear initially from the message boards it's because anonymous apps are assumed to be for CPUs. on Collatz they do not have this problem. Maybe Slicker can help here!
46) Message boards : Number crunching : time to shut down milkyway_gpu? (Message 35641) Posted 14 Jan 2010 by cenit Post: Is the concept of milkyway_gpu still considered? http://milkyway.cs.rpi.edu/milkyway_gpu/ Wouldn't be better if milkyway is all in a single project (even if someday you will give GPU different work units)? And what about the new app that was able to do work also on single precision devices and that Cluster Physik ported to CAL but was never used?
47) Message boards : Number crunching : Testing ATI Application Availability (Message 35637) Posted 14 Jan 2010 by cenit Post: Will this break things for users not using a GPU app? I can't see how. Maybe the big problem would arise whenever another project comes out with a GPU app and <count>0.5</count>. Then we could have conflicts on the GPU... or really big slow downs... Am I wrong?
48) Message boards : Application Code Discussion : Source Code of ATi app (Message 35589) Posted 13 Jan 2010 by cenit Post: and after this you still say there's not magic? Thanks for sharing a bit of your code. It's great to see how you can really optimize apps. I'm not really used to work on nvidia [and on ATi, too!], but I will ask to some friends (and colleagues) if someone knows how they implement the exp
49) Message boards : Application Code Discussion : Source Code of ATi app (Message 35526) Posted 12 Jan 2010 by cenit Post: ok! I asked it because I want to see your magic!
50) Message boards : Application Code Discussion : Source Code of ATi app (Message 35460) Posted 11 Jan 2010 by cenit Post: now that the ATi app is a stock app (and no more only a gift from Gipsel - thanks man!), could we have the source code, owing to your GPL promise?
51) Message boards : Number crunching : MW Preferences are Gone! (Message 35069) Posted 4 Jan 2010 by cenit Post: there's still the problem with profiles. I (and many others here) cannot create a profile: when we save it, a webpage with "Successful" come up, but the profile never get visible. If I retry, I find the fields still filled in (so the profile is in the db), but they never get published!
52) Message boards : Number crunching : Server crash is a good opportunity to upgrade it (finally) (Message 34582) Posted 16 Dec 2009 by cenit Post: How are the updates to the applications to refine background star distribution mentioned about a month ago coming? no news? another small thing: I had a profile here on milkyway, and the fields are already filled if I try to recreate it. But it seems that something is wrong in the database, because it gets accepted but never become visible.
53) Message boards : Application Code Discussion : CUDA for Milkyway@Home (Message 34398) Posted 9 Dec 2009 by cenit Post: This issue should be resolved in the latest version (0.24) available on BOINC. which is not available in code repository...
54) Message boards : Application Code Discussion : GPU app teaser (Message 32326) Posted 12 Oct 2009 by cenit Post: What did I get from that? A load of work and nothing else. Though it is of little value, you have my thanks and admiration. For what it is worth, I repeat the thanks ... Dear Gipsel, you have my thanks and admiration too. Your dedication to this project is really fantastic, without even being in the MW team you seem to give the best support.
55) Message boards : Number crunching : 3rd.in - optimized apps (Message 31334) Posted 22 Sep 2009 by cenit Post: system32 and SysWOW64 is the same directory. And there is no 64bit version of dll. Just don't use a 32 bit filemanager! Win64 mirrors the content of the SysWOW64 directory into system32 for all 32 bit programs. Be sure to use the explorer or use just the command line. I'm sorry CP, but the reality is a bit different: in short 64-bit DLL's are in the system32 directory, and 32-bit DLL's are in the SysWow64 directory. This is because redirector works on SysWOW64, while system natively works on system32 (it's a problem from the past, for compatibility reasons) You are sorry for what? That you misunderstood what I've written? ;) I know how it works and I've correctly described what happens when someone is using a 32bit program to access the system32 directory. The WOW64 layer redirects all accesses by 32bit programs to system32 into the SysWOW64 directory. Effectively he sees SysWOW64 as system32 directory. That is the reason he didn't see the 64bit dlls as long as he used a 32bit file manager. He used another one and that problem was solved. Quite simple. yeah, I'm sorry that I misunderstood what you've written ... ooops!
56) Message boards : Number crunching : 3rd.in - optimized apps (Message 31281) Posted 21 Sep 2009 by cenit Post: system32 and SysWOW64 is the same directory. And there is no 64bit version of dll. Just don't use a 32 bit filemanager! Win64 mirrors the content of the SysWOW64 directory into system32 for all 32 bit programs. Be sure to use the explorer or use just the command line. I'm sorry CP, but the reality is a bit different: in short 64-bit DLL's are in the system32 directory, and 32-bit DLL's are in the SysWow64 directory. This is because redirector works on SysWOW64, while system natively works on system32 (it's a problem from the past, for compatibility reasons) http://msdn.microsoft.com/en-us/library/aa384187(VS.85).aspx
57) Message boards : Number crunching : 3rd.in - optimized apps (Message 30822) Posted 14 Sep 2009 by cenit Post: 6.10.4 has a small problem where it tries to run work in last in first out method and does the waiting to run thing. Try going back to 6.10.3 instead. You can adjust how many run in the app_info <coproc> area. Thanks a lot I remember of having found a bug in 6.10.3 which was causing me some problems... I think I'll wait for 6.10.5. Reducing the queue, the problem goes away and, at the end, i'm not putting too much strain on the server because I do not work really much on milkyway! What about the coproc area? Should I put count on 0.33 if I'm understanding well so that I could have 3 wu at the same time?
58) Message boards : Number crunching : 3rd.in - optimized apps (Message 30808) Posted 14 Sep 2009 by cenit Post: as you can see from the previous thumbnail, I'm seeing strange behaviour from milkyway 0.20 app. Only one workunit runs at a time and many starts but not finish. As you can also see wall time is a bit high for having done only a fraction of the work of those work-units... What's going on? I must say that when boinc resumes those work-units it starts from 0% and so reported time is always under 60s (ATi 4770)

Previous 20