Computing Resources: Difference between revisions

From VrlWiki
Jump to navigation Jump to search
Jadrian Miles (talk | contribs)
No edit summary
Jadrian Miles (talk | contribs)
Line 39: Line 39:
===CS Department Compute Grid===
===CS Department Compute Grid===
The CS department runs a huge cluster of machines that are managed by the Sun Grid Engine.  Eventually all the idle machines in the department will be added to the resource pool that the SGE can assign jobs to.  Check out [http://cs.brown.edu/system/hardware/cluster/ the CS department's documentation] to learn more about the grid.
The CS department runs a huge cluster of machines that are managed by the Sun Grid Engine.  Eventually all the idle machines in the department will be added to the resource pool that the SGE can assign jobs to.  Check out [http://cs.brown.edu/system/hardware/cluster/ the CS department's documentation] to learn more about the grid.
David McClosky's written a (supposedly) nice grid engine wrapper called [http://www.cs.brown.edu/~dmcc/hogwash/ Hogwash].  Might be worth checking out, too.


[[Category:IT Tools]][[Category:Hardware]]
[[Category:IT Tools]][[Category:Hardware]]

Revision as of 00:43, 11 February 2009

Sometimes even non-interactive programs, like diffusion data batch processing, can be very resource-intensive. We have a couple different options for big iron to throw at such tasks.

sixg

The graphics group owns its own box with six gigs of RAM and more than six gigahertz total (over three processors) of processor speed, hence the name "sixg". There's no special mechanism for submitting jobs; simply ssh sixg and run commands as you normally would.

Other Fast Machines

  • aristotle
  • bun
  • tetra
Host       CPU Cache  CPU Type                      CPU Speed  Memory  IP Address
---------  ---------  ----------------------------  ---------  ------  --------------
bach                  Athlon 64 X2 Dual Core 3800+             4.0 GB  128.148.38.156
butler     1024 MB    Athlon XP 2700+                                  128.148.37.35
daisy      3071 MB    Intel Core 2 Quad Q6600       2.40GHz            128.148.38.177
extend     1023 MB    Athlon 64 Processor 3000+                        128.148.37.33
fuzzy      1023 MB    Athlon 64 Processor 3000+                        128.148.33.215
george                Athlon 64 X2 Dual Core 3800+             2.0 GB  128.148.38.141
naboo      2047 MB    Athlon 64 X2 Dual Core 3800+                     128.148.33.217
pitman                Intel Core 2 Quad Q6600                  4.0 GB  128.148.38.110
point                 Intel Core 2 Quad Q6600                  4.0 GB  128.148.33.31
sargent               Intel Core 2 Quad Q6600                  4.0 GB  128.148.38.130
scope                 Athlon 64 X2 Dual Core 3800+             2.0 GB  128.148.31.142
skirt      3071 MB    Intel Core 2 Quad Q6600       2.40GHz            128.148.31.24
staff       511 MB    Athlon XP1800+                                   128.148.37.20
stereo                Athlon 64 X2 Dual Core 3800+             2.0 GB  128.148.31.140
stone                 Athlon 64 X2 Dual Core 3800+             2.0 GB  128.148.31.139
transit               Athlon 64 X2 Dual Core 3800+             1.0 GB  128.148.38.148
udall                 Athlon 64 X2 Dual Core 3800+             2.0 GB  128.148.33.209
unnamed    1023 MB    Athlon 64 Processor 3000+                        128.148.38.174
wheat                 Athlon 64 X2 Dual Core 3800+             2.0 GB  128.148.31.88
wideload              Intel XEON                               512 MB  128.148.38.140

CS Department Compute Grid

The CS department runs a huge cluster of machines that are managed by the Sun Grid Engine. Eventually all the idle machines in the department will be added to the resource pool that the SGE can assign jobs to. Check out the CS department's documentation to learn more about the grid.

David McClosky's written a (supposedly) nice grid engine wrapper called Hogwash. Might be worth checking out, too.