I wan't to crunch einstein@home with my Ultra 30 (with a Ultra Sparc II 300 MHz CPU). How long are the typical crunching times for this CPU ?
I have attached to the project, but the estimated runtime is after some hours about 100 hours. This is a litte bit difficult to complete a work unit within the deadline, because this system is not to often running...
Copyright © 2024 Einstein@Home. All rights reserved.
Crunching times on UltraSparc II
)
For a system that old the runtime doesn't seem unreasonable.
If your system can run linux/bsd apps there's a beta client available than runs ~1.8x as fast as the standard one.
http://einstein.phys.uwm.edu/app_test.php
If you can run WINE, and get the 4.x boinc client working akos's C40 optimized app should give you a ~3x speed up.
Otherwise until a new offcial app's released I think you're out of luck. IIRC there're only a few hundred solaris machines on the project total, so compiling beta apps for them isn't a priority. In the mean time, you might want to look for a project with more forgiving WU sizes or deadlines for your machine.
RE: If your system can run
)
No, a other OS is no option. Also it is a SPARC, so i386 binaries would not run on this system.
So far I know, WINE only maps API calls. So it is not posible to let a i386 binary run on sparc.
I thought for einstein as primary or as backup project for this system. But this depends on the runtimes...
My mate got hold of an old
)
My mate got hold of an old sun workstation. I will have a look at it on the week-end. Since I never had a sun workstation, I am very interested in seeing what this is all about. Also of course how well it copes with Einstein, hehe.
I shall report back with some more information when at hand.
:
your thoughts - the ways :: the knowledge - your space
:
I have to admit that the
)
I have to admit that the current official Solaris App is indeed somewhat slow. I just wanted you to know that there is being worked on a new one, though it may take a while 'till it's out. It will probably be announced here.
BM
BM
RE: I have to admit that
)
Thank you very much, Bernd.
Btw. is einstein floating, integer-, cache or memory(bandwith) intensive ?
I am happy to hear that a new
)
I am happy to hear that a new version is under development. It is really little bit slow - crunching times for 1 WU on my SPARC 1.0 GHz is around 106,000 seconds and on my SPARC 1.5GHz around 76,000 seconds.
But better than nothing... :-)
RE: I am happy to hear that
)
That's painful. :( Between 2.5 and 3x slower than my athlon1500 running the stock client.
RE: Btw. is einstein
)
Mainly FPU. Once the FP code is fast enough, memory bandwith might come into play, but currently we're far from it.
BM
BM
RE: RE: Btw. is einstein
)
While granting that it's heavily dependent on architecture, is "far from it" approximately a factor of a half dozen or so, a few dozen, hundreds, something even huger?