Welcome to MilkyWay@home

Posts by tomd@perso.be

1) Message boards : Number crunching : N-Body long processing time (Message 62222)
Posted 27 Aug 2014 by tomd@perso.be
Post:
I'll avoid n-body then.

Thank you very much!

thomas
2) Message boards : Number crunching : N-Body long processing time (Message 62220)
Posted 27 Aug 2014 by tomd@perso.be
Post:
ps_nbody_08_05_orphan_sim_1_1405680903_433234_3 using milkyway_nbody version 142 was supposed to run for 4.5 hours (approx.) but ran for 33h. It was clear from the beginning that it would take that long, so the percentage of completion was OK but the scheduled length was 7-8 times to short.
It ran OK and didn't fail.

I see that I have other 1.42 simulations (and the actual one will take around 20-30h if percentages are correct instead of 35 minutes as planned).

I have 2 questions:

1) Am I wasting my time on these? i.e. Is my computer for some reason much slower on these jobs than it should be? And therefore, should I avoid these jobs (for my own sake and that of the project)?

2) I am running other projects. Are they going to be disadvantaged?
What I mean is: if I receive credits based on an estimated 4.5h job when the job actually ran 8 times longer, will the other projects be queued because boinc thinks milkyway@home hasn't received enough "time-share"? Or does boinc take into account the actual cpu run-time of different projects and therefore will compensate for long run-times of milkyway (and not allow it 8 times more time-share than other projects)?

Thomas




©2023 Astroinformatics Group