ng the scheduler takes to submit, allocate, reserve, and activate a
1,000+ CPU job, I think you'll like that. This is really nothing to do with
"Linux clusters" as it's largely a job scheduler issue and most job schedulers
support multiple platforms.
John Vert
Development Manag
MPI stack. We are looking at both of these for the next release but they
didn't make V1.
So like most product decisions, we didn't "have to do this" it was just
the normal tradeoff you make between features and schedules with a
healthy dose of security paranoia thrown into t
tends
to drop dramatically as soon as someone mentions Windows or Microsoft.
John Vert
Development Manager
High Performance Computing
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Robert G. Brown
Sent: Tuesday, April 03, 2007 7:59 AM
To: Bill Bryce
Cc: beo
practical experience.
John Vert
Development Manager
Windows High Performance Computing
> -Original Message-
> From: Mark Hahn [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 13, 2006 6:22 PM
> To: John Vert
> Cc: beowulf@beowulf.org
> Subject: RE: [Beowulf] MS HPC... Oh d
ck through Winsock
Direct. This enables low-latency usermode I/O at the sockets level. Any
application that uses sockets will benefit from the high speed
interconnect without relinking or recompiling.
A C-style ABI is pretty straightforward, but once you throw Fortran a
At the risk of starting another religious flame war, I'll point out that
if you want to run a Windows application, you might want to consider a
Windows cluster. http://www.microsoft.com/hpc has more information.
John Vert
-Original Message-
From: [EMAIL PROTECTED] [mailto:[
