Posts by Arun
1)
Message boards : Number crunching : Checkpointing ( Message 4144 )Posted 3327 days ago by Arun Okay, I recieved quite a few of the Wu's (about 220, musta been putting in calls just at the right time) across my Parm but will run them as fast as can ... :) ... I should have them run out by the morning. You sure did get a lot of the WUs ! Looks like the FLOPS estimate is more closer to the actual running time. With checkpointing it may take different time on other hosts with similar resources. Thanks for your feedback. Arun |
2)
Message boards : Number crunching : Checkpointing ( Message 4142 )Posted 3327 days ago by Arun
Yes, also if the number of tasks your client is getting based on the new FLOPS count for each complex is appropriate for your client setting and host cpu speed. Related discussion . Thanks for your feedback. Arun |
3)
Message boards : Number crunching : Checkpointing ( Message 4140 )Posted 3327 days ago by Arun I had at least two wu's in the last batch that successfully paused to allow other projects in BOINC to crunch and then resumed to finish. Both had an initial estimated work time of about 7hrs20min, and actually completed in about 2 hours. Pause was at about 1hr40min. We have distributed 300 WUs with revised FLOPS estimate. Please give your feedback for these workunits. Thanks Arun |
4)
Message boards : Number crunching : Cobblestones ( Message 4135 )Posted 3330 days ago by Arun Hmmm, that sounds interesting. Yes, please let the project team know if you find something on that. In the meantime, Arun could try commenting out the boinc calls in the charmm code and see if the time calls are still being made. If not, then that points in the direction you are thinking. Andre and David, Thanks for the informative discussion. I used gprof profiling tool and found that the times() function is executed 7.02% of the time, which took 5.12 seconds out of the total 72.98 seconds for this charmm execution. times() was the 3rd most time consuming function after enbfs8 and ephifs fortran calls. The output of strace also showed that times() function is called many times. Any suggestions ? David, any information you can find will be useful. cheers Arun |
5)
Message boards : Number crunching : Deadlines are very short. ( Message 4132 )Posted 3331 days ago by Arun
Thanks for your feedback. Your estimates are very good. We will be distributing 1tng and 1abe for 320 conformations and 20 rotations with these flops (+10%) from next time. 1tng - 22,000,000,000,000 1abe - 20,000,000,000,000 We are doing testing using these FLOPS count. Arun |
6)
Message boards : Number crunching : No work available for x64 Windows machines? ( Message 4131 )Posted 3331 days ago by Arun Hello everyone, I'm getting always this annoying error message when trying to do some testing... *sob sob* ;-) Cori, as Bob said, are you using 6.2.x client ? |
7)
Message boards : Number crunching : Deadlines are very short. ( Message 4124 )Posted 3331 days ago by Arun As the title says, the deadlines are very short for this run. We have created more workunits and have increased the deadline to 5 days. Thanks for your feedback and help. Arun |
8)
Message boards : Number crunching : Cobblestones ( Message 4113 )Posted 3332 days ago by Arun Good point. No, I've not been able to figure out why these system calls to get the time of day on linux are made a gazillion times per run. I do think that this might cause the massive difference in runtime between linux and windows. The runtime difference issue is already on the project's to-do list, so I'll make sure that whatever notes I have on this will be passed on to the next person trying to crack this issue. The problem of execution time differing between windows and linux need to be solved before we move on to fixed credit based on FLOPS. I will be working on this issue tomorrow. Andre, can you pass me the notes you have on this issue ? cheers, Arun |
9)
Message boards : Number crunching : Checkpointing ( Message 4112 )Posted 3332 days ago by Arun
Thanks for letting us know checkpointing is working fine. The model we are running right now is a simple model. And since we are checkpointing at the end of each confirmation, the time between each checkpointing is low. We are developing newer models which will have higher time interval (~6 minutes) between each checkpointing. For the current model the time is around 70-80 seconds on a old P4 machines and 16-20 seconds on a dual core machines for 1abe and 1tng complexes. Thanks for your feedback and help ! Arun |
10)
Message boards : Getting started : Invitation Code? ( Message 4110 )Posted 3332 days ago by Arun We are working on opening Docking@Home to the public. Hopefully it will happen soon. Please check your PMs. |
Next 10 posts