SCIENTIFIC-LINUX-USERS Archives

August 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for Scientific Linux users worldwide <[log in to unmask]>
Date:
Sun, 24 Aug 2014 15:46:22 -0400
Reply-To:
John Lauro <[log in to unmask]>
Content-Transfer-Encoding:
7bit
Subject:
From:
John Lauro <[log in to unmask]>
Content-Type:
text/plain; charset="utf-8"
In-Reply-To:
MIME-Version:
1.0
Comments:
To: Paul Robert Marino <[log in to unmask]> cc: Brandon Vincent <[log in to unmask]>, Lee Kin <[log in to unmask]>, "[log in to unmask]" <[log in to unmask]>, Nico Kadel-Garcia <[log in to unmask]>
Parts/Attachments:
text/plain (23 lines)
The recommendation changed with 5.5.  
http://blogs.vmware.com/performance/2013/09/deploying-extremely-latency-sensitive-applications-in-vmware-vsphere-5-5.html

"... However, performance demands of latency-sensitive applications with very low latency requirements such as distributed in-memory data management, stock trading, and high-performance computing have long been thought to be incompatible with virtualization.
vSphere 5.5 includes a new feature for setting latency sensitivity in order to support virtual machines with strict latency requirements."


----- Original Message -----
> From: "Paul Robert Marino" <[log in to unmask]>
> To: "Nico Kadel-Garcia" <[log in to unmask]>
> Cc: "John Lauro" <[log in to unmask]>, "Brandon Vincent" <[log in to unmask]>, "Lee Kin"
> <[log in to unmask]>, "[log in to unmask]" <[log in to unmask]>
> Sent: Sunday, August 24, 2014 3:27:39 PM
> Subject: Re: about realtime system
...
> By the way one of those stock exchanges is where the VMware engineers
> told us never to use their product in production. In fact we had huge
> problems with VMware in our development environments because some of
> our applications would actually detect the clock instability in the
> VMware clocks and would shut themselves down rather than have
> inaccurate audit logs. as a result we found we had trouble even using
> it in our development environments.

ATOM RSS1 RSS2