skip to main | skip to sidebar

SciLINC Dev

... progress, issues and development notes on the Scientific Literature Indexing on Networked Computers (SciLINC) project

Tuesday, October 03, 2006

BOINC Suitability

As a rule of thumb, if your application produces or consumes more than a gigabyte of data per day of CPU time, then it may be cheaper to use in-house cluster computing rather than volunteer computing.

Which applications are suitable for BOINC?

Posted by Ron Parker at 1:42 PM

No comments:

Post a Comment

Newer Post Older Post Home
Subscribe to: Post Comments (Atom)

Links

  • SciLINC
  • Botanicus Blog
  • Botanicus

Blog Archive

  • ►  2007 (5)
    • ►  May (1)
    • ►  January (4)
  • ▼  2006 (43)
    • ►  December (7)
    • ►  November (14)
    • ▼  October (22)
      • Running BOINC uppercase Demo Standalone
      • Compiling BOINC uppercase Sample on Linux
      • Shared Memory Errors in Standalone BOINC Applications
      • Standalone BOINC Application dlopen Failure
      • Cannot Restore Segment Prot after Reloc Error
      • SIGSEGV Running Standalone BOINC Application
      • Improving compile speeds on Linux
      • Configuring BOINC for Linux from CVS
      • BOINC for intra-organizational computing
      • Scrolling wide pre-formatted text
      • Adding repositories to Fedora 5
      • Fixing coLinux Fedora's passwd program
      • Dvorak on Fedora Core Linux
      • Building BOINC Applications on Windows
      • Making a Large Sparse coLinux Disk Image
      • Spy Hill Research BOINC Developers' Notes
      • BOINC Server Planning
      • BOINC server bottlenecks
      • Pertinent BOINC Server Software Prerequisities
      • BOINC Suitability
      • BOINC
      • SciLINC - Scientific Literature Indexing on Networ...