Posts by BitSpit

1) Message boards : Number crunching : Problems with version 5.96 (Message 53561)
Posted 5 Jun 2008 by BitSpit
Post:
And just to confirm that there's either a problem with the jobs or the validator, my list of invalidated FRA_t401_CASP8_2PRV_2ICG_1_IGNORE_THE_RESTt401_1_aaT0401_2ICGA_13_0001_3601 jobs so far:

http://boinc.bakerlab.org/rosetta/result.php?resultid=168445437
http://boinc.bakerlab.org/rosetta/result.php?resultid=168445425
http://boinc.bakerlab.org/rosetta/result.php?resultid=168460452
http://boinc.bakerlab.org/rosetta/result.php?resultid=168390070
http://boinc.bakerlab.org/rosetta/result.php?resultid=168420107
http://boinc.bakerlab.org/rosetta/result.php?resultid=168419121 (invalid for second person also)
http://boinc.bakerlab.org/rosetta/result.php?resultid=168363001
http://boinc.bakerlab.org/rosetta/result.php?resultid=168478613
http://boinc.bakerlab.org/rosetta/result.php?resultid=168500618
http://boinc.bakerlab.org/rosetta/result.php?resultid=168496136
http://boinc.bakerlab.org/rosetta/result.php?resultid=168445210 (invalid for second person also)
http://boinc.bakerlab.org/rosetta/result.php?resultid=168412886
http://boinc.bakerlab.org/rosetta/result.php?resultid=168490942
http://boinc.bakerlab.org/rosetta/result.php?resultid=168338736
http://boinc.bakerlab.org/rosetta/result.php?resultid=167854925 (unique result: my invalid run produced 686 decoys. The reissued run produced 126 and was valid.)

Looking at that last result, I think you have a problem with the validator not handling high decoys.
2) Message boards : Number crunching : minirosetta v1.25 bug thread (Message 53435)
Posted 29 May 2008 by BitSpit
Post:
To me, 1.24 is looking a lot better than 1.25.

First up is t0391 LOOP IGNORE. These had a tendency to get stuck but still use CPU time and increase the time and percentage. They would run at least twice my selected runtime before I noticed. Upon restarting BOINC, they would go back to between 1 and 3 hours.

http://boinc.bakerlab.org/rosetta/result.php?resultid=166663997
http://boinc.bakerlab.org/rosetta/result.php?resultid=166584405
http://boinc.bakerlab.org/rosetta/result.php?resultid=166495787
http://boinc.bakerlab.org/rosetta/result.php?resultid=166469516
http://boinc.bakerlab.org/rosetta/result.php?resultid=166456690
http://boinc.bakerlab.org/rosetta/result.php?resultid=166451086 (got stuck 4 times. I aborted it.)

Next is 2oq2a BOINC CASP8 LOOPRELAX. They crashed with Maximum disk usage exceeded

http://boinc.bakerlab.org/rosetta/result.php?resultid=166703386
http://boinc.bakerlab.org/rosetta/result.php?resultid=166702956
http://boinc.bakerlab.org/rosetta/result.php?resultid=166700665
http://boinc.bakerlab.org/rosetta/result.php?resultid=166705432


I've reduced my runtime from 8 hours to 4 to see if it helps.
3) Message boards : Number crunching : Computer array crunching? (Message 53356)
Posted 26 May 2008 by BitSpit
Post:
Okay, I finally got around to whipping up a page for my setup. It's at http://splicedcollective.org/armada/ It has my SMP kernel, control script, directory structure layout, and some pictures of my stuff.
4) Message boards : Number crunching : Computer array crunching? (Message 53258)
Posted 22 May 2008 by BitSpit
Post:
I ran 16 machines in the basement here at one point. Trust me. The temperature will go over 80. Computers double as decent space heaters.

And to correct a few of dcdc's numbers, and Q6600 has a multiplier of 9 so...

Stock Q6600, 2.4GHz, 266 FSB, DDR2 553 minimum
Q6600 @ 3.0GHz, 333 FSB, DDR2 667 minimum
Q6600 @ 3.2GHz, 356 FSB, DDR2 800 or quality 667 with some slightly loosened timing
Q6600 @ 3.6GHz, 400 FSB, DDR2 800
5) Message boards : Number crunching : Computer array crunching? (Message 53215)
Posted 21 May 2008 by BitSpit
Post:
2)Your current system seems about $50 cheaper than a Dell box with the same quad chip, 3gig of ram (instead of your 1gig), a 500g drive (instead of your 0g drive), a case, cd/dvd drive, keyboard, and mouse and maybe a few other things...so...although Dell might be a slight monopoly, why not just buy a bunch of the same Dell machines? I would understand if it was physical size dimensions issue and/or power sucking issue...care to elaborate? Just wondering. Heck, you could sell the 500g drives for $100 a pop not to mention the dvd/cd drive for $25.


I'm using 2GB on my quads, not 1. I'm more concerned about the quality and capability of parts rather than quantity. A stock Q6600 gets around 1650 RAC (at least for me). Pushing it to 3GHz gets around 2400. That's not something as easily done with a cheap Dell. The Dell also wouldn't be designed for 24/7 overclocked use. Building it myself lets me design it how I want.

Anyway, overall I'd love to learn a little bit more about where you bought your equipment, how it was set up, some pics, etc. I'm technical, I just haven't played around with diskless systems, Linux operating systems, etc.


I mostly buy my parts from Mwave, Fry's (they've been selling retail Q6600s for $200 or less), and Directron.

I started doing this netbooting stuff about 4 1/2 years ago with Athlon XPs running Find-a-Drug. Part of it was to simply learn a few things about Linux. Some people download Ubuntu. I take on a crazy project. The setup has been through a couple revisions but it's at a state that mostly satisfies me. I'm probably a little more hardcore with my setup than most would be. I have some networked I/O controllers to monitor power that are also directly wired to the motherboard power switch and reset pins for those times when I need control at the hardware level.
6) Message boards : Number crunching : Computer array crunching? (Message 53211)
Posted 20 May 2008 by BitSpit
Post:
BS - how do you get around the problem of no swap file with your setup if all the physical memory is being used?


Make sure there's plenty available. :) Seriously, I allocate 512MB per core and set my preferences to allow 99% memory usage. This seems to be sufficient. The Linux version doesn't seem to require as much. I've only seen one job run out. The job crashed and BOINC simply loaded up the next task.

I disagree with the previous poster about onboard NICs. I've used several different boards and the onboard NIC always worked fine. The only problem was when the NIC was so new that it wasn't supported by the version of Linux I was using.


I've noticed the onboard NICs tend to drop packets during the boot process before the kernel driver loads which is why I made my comment. I'd much rather spend a few dollars on a NIC than throttle the server.
7) Message boards : Number crunching : Computer array crunching? (Message 53203)
Posted 20 May 2008 by BitSpit
Post:
I'm running what could be called a 10 computer array. I'm using LTSP 4.2 which is a netbooting Linux package. Each system loads off a central server. The server is the only computer that has a hard drive (well except for my laptop but I netboot when it's docked). It does take some work to get things set up, but once the first system is setup, all the others simply get added to a configuration file. The hardest part has been compiling a kernel with SMP support so I could get dual and quad core support. The other major issue is the network card. Don't bother with the motherboard's onboard NIC unless it's Intel. All the others suck and cause problems. I personally like Broadcom's gigabit network cards because they're cheap (around $8) and they work with no effort. Now for my dedicated crunchers.

2007 Intel setup (started with this):
Intel E4400 overclocked to 3.2GHz
1GB generic 667 DDR2
Abit F-I90HD motherboard (do not recommend, I'm replacing these)
Generic 400W power supply
Broadcom gigabit NIC
$5 8MB ATI Rage Pro PCI video card

This uses 115W and gets roughly a 1,050 RAC

2008 Intel setup (switching to this):
Intel Q6600 overclocked to 3.0GHz
Asus P5K-VM motherboard
2GB Corsair XMS2-675 DDR2
Enermax Liberty 400W (80% efficiency plus no extra, unused cables)
Broadcom gigabit NIC
$5 8MB ATI Rage Pro

This uses 145W for a Q6600 B3 stepping (haven't checked G0) and gets around 2400 RAC, although this can go as high as 3,000/day if running primarily Rosetta Mini jobs (large L2 + Linux = crazy high points, granted credit up to 4.5x claimed).

I'm also not using any cases. I screw standoffs onto them and then place them onto cork-covered shelves. Never had any static issues with it and no worries about shorting.

The Q6600 setup does end up close to $450 (before I've spent another $40 on cooling) for one simple reason: I can't buy parts in bulk like Dell. Some of that cost can be lowered by using cheaper memory, a lower end motherboard, skipping the video card and using onboard. Even then, getting below $400 using quality parts will be difficult.

I really should get around to making a web page for this.
/me adds item to rarely checked to do list
8) Message boards : Number crunching : minirosetta v1.19 bug thread (Message 53020)
Posted 12 May 2008 by BitSpit
Post:
Bitspit, is that the root cause of the "no heartbeat from client in 31 secs" msgs?? Do you have a link to the trac item for this?


Yes, that usually is the cause of it. I don't know if there's an official bug report on it. I do know it's a question that shows up in the BOINC forums every few months where the explanation is given and they claim it would be too much effort to fix.
9) Message boards : Number crunching : minirosetta v1.19 bug thread (Message 53006)
Posted 12 May 2008 by BitSpit
Post:
More segfaults,on linux running 5.10.45 client.

Apparently there was a problem with the network connection and the client kept trying to reconnect.


That's usually caused by a known, unfixed BOINC flaw, not Rosetta. When BOINC is resolving a domain name, it blocks all other communication, including running tasks. If that continues past 30 seconds, things start failing/crashing. The only know workaround is changing the DNS timeout. That's done in resolv.conf (usually located at /etc/resolv.conf) by adding the line options timeout:2 That makes each attempt 2 seconds with the default of 2 retries per DNS server. You can play with the options some based on your number of DNS server but try not to go over 25 seconds.
10) Message boards : Number crunching : Running BOINC in LTSP 4.2 with custom SMP kernel (Message 52879)
Posted 6 May 2008 by BitSpit
Post:
After reading BitSpit's howto from the https://muzso.hu/node/3978 page.


Not my howto. Can't take credit for someone else's work.

However I did go back a couple times after that and turned off just about everything that I did not need for my hardware.


I remember trying that when I started compiling kernels. It didn't work well. I think the only thing I could safely leave out was sound.

I have not got boinc to run as a local app on my ltsp clients yet however I do get them all up to a bash shell. I'm fighting an ssh issue that maybe related to a mistake in the copy initramfs steps. I can get a bash shell but cannot telnet or ssh from the server into the client.


See http://wiki.ltsp.org/twiki/bin/view/Ltsp/LocalApps for ssh help.

For anyone interested in trying some of the diskless, netbooting Linux madness and you don't feel like compiling your own SMP kernel, you can download mine at http://splicedcollective.org/software/2.6.17.8-ltsp-p3-smp.zip It's the same as the stock LTSP 4.2 kernel except it has 4-core SMP support and it requires a P3 minimum.

A couple of additional useful notes. First, BOINC has a known flaw in its netcode. Whenever it does a DNS lookup, it halts all other network connections. That tends to be a problem when you're running over the network. The workaround is changing the DNS timeout. Open up /opt/ltsp/i386/etc/rc.sysinit and go to the section labeled "Setup the resolv.conf file." Add this line:

echo "options timeout:2">>/tmp/resolv.conf

This changes the timeout from the default 5 seconds to 2 seconds. You can play around with the timeout and retry (default 2) options but the important thing is to keep the total time resolving DNS at 25 seconds or less. Any longer and tasks WILL start crashing with the message "No heartbeat from core for 31 seconds" In my experience, once that starts happening, BOINC will start idling cores, erroring out the work queue, and possibly locking up the whole system requiring a reboot.

Second and while we're in resolv.conf, let's talk about setting the DNS servers. By default, LTSP sets the DNS server the same as your LTSP server. I don't like that. Also, it does not pick up any additional servers through DHCP. To change the servers, you'll need to edit rc.sysinit in the same resolv.conf section. To specify your own DNS servers, just append /tmp/resolv.conf with some echo statements. For example, to use OpenDNS:

echo "nameserver 208.67.222.222" >>/tmp/resolv.conf
echo "nameserver 208.67.220.220" >>/tmp/resolv.conf

To disable the default behavior of using the LTSP server for DNS, comment out or delete this line:

echo "nameserver ${DNS_SERVER}" >>tmp/resolv.conf

Finally, you can do some fun things using a screen script. On my setup, I have one created that does a multi-project setup. I can change a system's config file and choose what it will run (currently either BOINC or distributed.net). It also lets me set a flag for the system to either shutdown or reboot when the current program ends.
11) Message boards : Number crunching : Problems with version 5.90/5.91 (Message 50013)
Posted 24 Dec 2007 by BitSpit
Post:
The 1zpy__BOINC_TWIST_RINGS jobs don't even need 763MB. They only use around 122MB.

I hate to say it but I'm done with Rosetta. I've run out of patience. The whole 5.90 thing got me close but the currently flawed jobs have pushed me too far. All the 1zpy__BOINC_TWIST_RINGS are fatally flawed for Linux and these are the ONLY jobs being sent out. I should know. I burned through 70 of them with the abort command. I just can't take the declining quality of the project anymore.
12) Message boards : Number crunching : Problems with version 5.90/5.91 (Message 50006)
Posted 24 Dec 2007 by BitSpit
Post:
Major, major flaws in any 1zpy job with TWIST_RINGS and only those jobs.Any other 1zpy job runs properly. And before anyone blames my computers, I went through Thomas Leibold's computers and his results are showing the same problems.

1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_4256_0
1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_15109_0
1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_3990_0
1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_25051_0
1zpy__BOINC_TWIST_RINGS_MORE_SLIDESYMM_FOLD_AND_DOCK-1zpy_-native__2476_4607_0
1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_4333_0
1zpy__BOINC_TWIST_RINGS_MORE_SLIDESYMM_FOLD_AND_DOCK-1zpy_-native__2476_4804_0

And in particular, 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0

After it crashed, it was still listed as a running task, still accumulating CPU time but not actually running. It was even listed in the job list as a computation error. Message log:

9:02:00 AM	Starting 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0
9:02:00 AM	Starting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 using rosetta_beta version 591
9:02:02 AM	[file_xfer] Started upload of file 1q9a__BOINC_NO_SRL_TORSION_RNA_ABMIN-1q9a_-_2473_4714_0_0
9:02:38 AM	[file_xfer] Finished upload of file 1q9a__BOINC_NO_SRL_TORSION_RNA_ABMIN-1q9a_-_2473_4714_0_0
9:02:38 AM	[file_xfer] Throughput 29612 bytes/sec
9:09:19 AM	Sending scheduler request: To report completed tasks
9:09:19 AM	Reporting 1 tasks
9:09:24 AM	Scheduler RPC succeeded [server version 601]
9:09:24 AM	Deferring communication for 4 min 2 sec
9:09:24 AM	Reason: requested by project
9:47:51 AM	Starting BOINC client version 5.8.11 for i686-pc-linux-gnu
9:47:51 AM	log flags: task, file_xfer, sched_ops
9:47:51 AM	Libraries: libcurl/7.16.0 OpenSSL/0.9.8d zlib/1.2.3
9:47:51 AM	Data directory: /home/armada/nodes/armada5/bin/boinc
9:47:51 AM	Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU          4400  @ 2.00GHz
9:47:51 AM	Memory: 1011.04 MB physical, 0 bytes virtual
9:47:51 AM	Disk: 70.87 GB total, 64.30 GB free
9:47:51 AM	URL: http://boinc.bakerlab.org/rosetta/; Computer ID: 404492; location: (none); project prefs: default
9:47:51 AM	General prefs: from rosetta@home (last modified 2007-07-21 12:29:21)
9:47:51 AM	Host location: none
9:47:51 AM	General prefs: using your defaults
9:47:51 AM	Restarting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_3756_0 using rosetta_beta version 591
9:47:51 AM	Restarting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 using rosetta_beta version 591
11:07:57 AM	Aborting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0: exceeded disk limit: 129.67MB > 95.37MB
11:07:57 AM	Deferring communication for 1 min 0 sec
11:07:57 AM	Reason: Unrecoverable error for result 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 (Maximum disk usage exceeded)
11:08:02 AM	Computation for task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 finished
11:08:02 AM	Output file 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0_0 for task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 absent
11:08:03 AM	[error] Process 1936 not found
11:08:26 AM	Starting 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0
11:08:26 AM	Starting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 using rosetta_beta version 591
11:43:11 AM	Starting BOINC client version 5.8.11 for i686-pc-linux-gnu
11:43:11 AM	log flags: task, file_xfer, sched_ops
11:43:11 AM	Libraries: libcurl/7.16.0 OpenSSL/0.9.8d zlib/1.2.3
11:43:11 AM	Data directory: /home/armada/nodes/armada5/bin/boinc
11:43:11 AM	[error] State file error: result 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 is in wrong state
11:43:11 AM	Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU          4400  @ 2.00GHz
11:43:11 AM	Memory: 1011.04 MB physical, 0 bytes virtual
11:43:11 AM	Disk: 70.87 GB total, 64.30 GB free
11:43:11 AM	URL: http://boinc.bakerlab.org/rosetta/; Computer ID: 404492; location: (none); project prefs: default
11:43:11 AM	General prefs: from rosetta@home (last modified 2007-07-21 12:29:21)
11:43:11 AM	Host location: none
11:43:11 AM	General prefs: using your defaults
11:43:11 AM	Restarting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_3756_0 using rosetta_beta version 591
11:43:12 AM	Starting 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_16554_0
11:43:12 AM	Starting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_16554_0 using rosetta_beta version 591
13) Message boards : Number crunching : Problems with version 5.90/5.91 (Message 49997)
Posted 24 Dec 2007 by BitSpit
Post:
Two more jobs that got stuck and were killed by the watchdog:

1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_287
1zpy__BOINC_TWIST_RINGS_MORE_SLIDESYMM_FOLD_AND_DOCK-1zpy_-native__2476_200

Every job that I've had killed like that has been a 1zpy with TWIST_RINGS. The combination of the two is causing a problem.
14) Message boards : Number crunching : Problems with version 5.90/5.91 (Message 49988)
Posted 23 Dec 2007 by BitSpit
Post:
Okay, 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470 problems are NOT limited to Linux. I just had one on a Windows machine get killed by the watchdog:

http://boinc.bakerlab.org/rosetta/result.php?resultid=128341472
15) Message boards : Number crunching : Problems with version 5.90/5.91 (Message 49972)
Posted 23 Dec 2007 by BitSpit
Post:
There seems to be a problem with the 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470 jobs. So far, the watchdog has killed 6 out of 7 jobs.

http://boinc.bakerlab.org/rosetta/result.php?resultid=128342607
http://boinc.bakerlab.org/rosetta/result.php?resultid=128342579
http://boinc.bakerlab.org/rosetta/result.php?resultid=128342572
http://boinc.bakerlab.org/rosetta/result.php?resultid=128344197
http://boinc.bakerlab.org/rosetta/result.php?resultid=128342732
http://boinc.bakerlab.org/rosetta/result.php?resultid=128342735
16) Message boards : Number crunching : Common Denominator?: compute errors and zero cpu usage (Message 49970)
Posted 23 Dec 2007 by BitSpit
Post:
I remember reading about this a couple years ago. This is a known BOINC problem. From what I remember, it's net code uses blocking calls. The problem is that those blocking calls prevent BOINC from communicating with any running app. If I'm remembering correctly, the BOINC devs have said that it's broken by design and don't want to put in the effort required to fix it.

Edit: Here's a good explanation of the problem.
17) Message boards : Number crunching : Problems with version 5.90/5.91 (Message 49943)
Posted 22 Dec 2007 by BitSpit
Post:
I suspended some jobs to force a couple of 5.91 jobs to run. I'm happy to report they ran without problems. 5.91 seems good.
18) Message boards : Number crunching : Problems with version 5.90/5.91 (Message 49864)
Posted 21 Dec 2007 by BitSpit
Post:
I just finished going through the top 1000 computers and checking the results of the Linux systems. It's a very sad state. I only found 4 jobs that ran 100% properly. The rest either:

were marked invalid because the CPU time wasn't recorded
ignored the CPU runtime preference and ran up to four times the preference
reported properly because BOINC was restarted

I've stopped all job requests here on all systems (Windows too). I've double my runtime preference to squeeze more out of the 5.89 jobs. When those are done and if there's no fix for the Linux systems, I'm finished with Rosetta.
19) Message boards : Number crunching : Diskless crunching methods (Message 49678)
Posted 14 Dec 2007 by BitSpit
Post:
I have seven Linux systems that currently netboot. I'm using LTSP 4.2 with the local apps option and a custom SMP kernel. When one of the systems boots, part of the DHCP response tells it to download a network boot loader. The loader then downloads the Linux RAM disk image. From there it boots like a normal Linux system, just over a network. After booting, it runs a custom script that then loads the distributed computing client indicated in a configuration file. It will also restart a client or start a different one when the current one stops running.

All the systems are either dual or quad cores. I configure each one with 512MB RAM per core. The Linux RAM disk eats about 8MB of that. There's no swap file but I've never had a problem with lack of memory. Linux has much better memory management than Windows. The only PITA part is finding network cards that work well. In that area, I can tell you Realtek is garbage.
20) Message boards : Number crunching : Problems with web site (Message 49508)
Posted 8 Dec 2007 by BitSpit
Post:
Quick little tip for bypassing the spam filter. If you're posting a link to a specific task, work unit, or computer, to can add a ampersand ( & ) to the end of the URL and not have to edit the post. Examples:

Computer: http://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=186636&
Computer results: http://boinc.bakerlab.org/rosetta/results.php?hostid=186636&
Job result: http://boinc.bakerlab.org/rosetta/result.php?resultid=125044738&


Next 20



©2020 University of Washington
https://www.bakerlab.org