I must have missed them.

I had two successful, valid results.

one and two

And this one died before getting started.

System specs...

6/6/2007 11:31:10 AM||Starting BOINC client version 5.10.2 for windows_intelx86
6/6/2007 11:31:10 AM||log flags: task, file_xfer, sched_ops, cpu_sched
6/6/2007 11:31:10 AM||Libraries: libcurl/7.16.1 OpenSSL/0.9.8e zlib/1.2.3
6/6/2007 11:31:10 AM||Data directory: C:Program FilesBOINC
6/6/2007 11:31:11 AM||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 2.80GHz [x86 Family 15 Model 2 Stepping 7]
6/6/2007 11:31:11 AM||Processor features: fpu tsc sse sse2 mmx
6/6/2007 11:31:11 AM||Memory: 446.98 MB physical, 1.78 GB virtual
6/6/2007 11:31:11 AM||Disk: 55.88 GB total, 30.32 GB free
6/6/2007 11:31:11 AM|vtu@home|URL: http://boinc.vtu.lt/vtuathome/; Computer ID: 4165; location: home; project prefs: default
6/6/2007 11:31:11 AM|Cosmology@Home|URL: http://cosmos.astro.uiuc.edu/cosmohome/; Computer ID: 65; location: (none); project prefs: default
6/6/2007 11:31:11 AM|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 932940; location: (none); project prefs: default
6/6/2007 11:31:11 AM|BOINC alpha test|URL: http://isaac.ssl.berkeley.edu/alpha/; Computer ID: 1716; location: (none); project prefs: default
6/6/2007 11:31:11 AM|Pirates@Home|URL: http://pirates.spy-hill.net/; Computer ID: 37229; location: (none); project prefs: default
6/6/2007 11:31:11 AM|APS@Home|URL: http://www.apsathome.org/; Computer ID: 298; location: home; project prefs: default
6/6/2007 11:31:11 AM|DepSpid|URL: http://www.depspid.net/; Computer ID: 777; location: home; project prefs: default
6/6/2007 11:31:11 AM||General prefs: from BOINC alpha test (last modified 2007-05-20 01:05:30)
6/6/2007 11:31:11 AM||Host location: none
6/6/2007 11:31:11 AM||General prefs: using your defaults
6/6/2007 11:31:11 AM||Preferences limit memory usage when active to 424.64MB
6/6/2007 11:31:11 AM||Preferences limit memory usage when idle to 442.51MB
6/6/2007 11:31:11 AM||Preferences limit disk usage to 27.94GB

---

Kathryn :o)
The BOINC FAQ Service
The Unofficial BOINC Wiki
The Trac System
More BOINC information than you can shake a stick of RAM at.

I had all successes with my workunits, which ran when I was away. :D

Full success on my ones. :-)
And I had much... :-D

Yes, actually I first got the Linux application working at the end of last week. I also finally compiled a working version of our application for Windows, which has been working since Tuesday or so.

Since then, we've had about 2500 workunits successfully completed, and we'll have a lot more coming soon.

---

Scott Kruger
Project Administrator, Cosmology@Home

First of all, thanks for the invitation, Scott (Guy here)

And... hello, fellow alpha test addicts ;)

Just finished my 2 first Windows WU's with success. Now that was short! About 10 seconds each. Tonight I'll run some Linux.

---

BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair

Yes, Ubuntu Linux on vmware and Windows without any problems :)

Great to hear it!

---

Scott Kruger
Project Administrator, Cosmology@Home

Hi Folks !

Running just fine on my system so far, Over 50 Wu's done all have run successfully so far. Running Apx. 15 seconds per wu per core for me.

Regards
G^R

---

Windows-XP-Pro, AMD 3800X2, 5.10.28

I ran a couple dozen WU in a 64-bit Linux Ubuntu 7.04. All ran successful, between 5 and 15 seconds.

One remark: There is a whole lot of upload going on, with files up to 44kB in size for a 10 second run. That makes for Boinc having its hands full with I/O. Probably a lot of debug info in the 44kB?

---

BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair

I ran a couple dozen WU in a 64-bit Linux Ubuntu 7.04. All ran successful, between 5 and 15 seconds.

One remark: There is a whole lot of upload going on, with files up to 44kB in size for a 10 second run. That makes for Boinc having its hands full with I/O. Probably a lot of debug info in the 44kB?

Yes and no; that's one thing that we're currently working on.

The reason the file is so large is that our application outputs the results of splines to the file, which are unnecessary. However, it's turning out to be difficult to fix this issue (Fortran is hard!).

Once we get it fixed, though, the size of the output files should be lowered by a factor of 50 or so.

---

Scott Kruger
Project Administrator, Cosmology@Home

Thanks for the invitation Scott. They seem to be doing just fine for Windows XP with client 5.8.16, though they take around 30-ish seconds on my Intel dual Xeon HT machine.

-Michael

I ran a couple dozen WU in a 64-bit Linux Ubuntu 7.04. All ran successful, between 5 and 15 seconds.

One remark: There is a whole lot of upload going on, with files up to 44kB in size for a 10 second run. That makes for Boinc having its hands full with I/O. Probably a lot of debug info in the 44kB?

Yes and no; that's one thing that we're currently working on.

The reason the file is so large is that our application outputs the results of splines to the file, which are unnecessary. However, it's turning out to be difficult to fix this issue (Fortran is hard!).

Once we get it fixed, though, the size of the output files should be lowered by a factor of 50 or so.

Will the work units eventually run longer than +/- 10 seconds? Now the frequent uploads and downloads make Boinc's transfer queue grow pretty quickly on a fast machine.

---

BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair

... They seem to be doing just fine for Windows XP with client 5.8.16, though they take around 30-ish seconds on my Intel dual Xeon HT machine.

-Michael

Don't worry, they took about 20-30 secs on my P4 boxes as well. ;-)

Will the work units eventually run longer than +/- 10 seconds? Now the frequent uploads and downloads make Boinc's transfer queue grow pretty quickly on a fast machine.

I was just considering that, actually.

Right now, we are running a legacy app using the BOINC wrapper application. It shouldn't be too difficult to send 25 or so input files as one tar.gz file and then make the wrapper queue them up, then send back the result as one file as well.

I'll work on that in the coming weeks, but for now I think we'll have to accept the fact that we're very IO-bound.

---

Scott Kruger
Project Administrator, Cosmology@Home

I've run a few units on my 32 bits Vista : all ran successful.

NB : this machine runs an optimized client and is claiming (and is granted) twice as much credits as my other PC for the same computing time. What kind of credit system do you use? Benchmark dependent?

---

Join us at Boinc.be

All successful runs on
- Vista 32
- Ubuntu 6.06 LTS 32
- PIII with 128MB RAM, Windows 2000

I have also only sucessfull runs on:

E6600 with Vista 64bit and 32bit BOINC
and E6300 with Ubuntu 7.04 32 bit - 2.6.20-16 lowlatency kernel...

The only problem I observed was with the Vista host. I saw that the BOINC manager was responding very slow, because of the lot of up- and downloads, and had two times a Windows explorer crash while crunching cosmology@home.
No crashes with other projects...

Hi Scott and fellow testers, now completed around 860 work units on each of two machines, 1st is a 32bit Vista Pro machine with Boinc 5.10.2 and the 2nd a Win XP Pro again with 5.10.2.
The Vista machne has encountered the following errored work units

wu_060707_230043_0
wu_060707_173548_1
wu_060707_185058_1
wu_060707_164621_0

Each failed work unit has the following out put:-

<core_client_version>5.10.2</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>params_060707_173548_1.ini</file_name>
<error_code>-119</error_code>
<error_message>MD5 check failed</error_message>
</file_xfer_error>

</message>

No problems with the XP Machine running a P4 3.2Ghz CPU