synchronize a "mocked" clock in a distributed system
in [Ruby]
|
Prev: [Q] synchronize a "mocked" clock in a distributed system
Next: [ANN] SmartImage 0.0.3 - simple yet powerful cross-platformthumbnail generation and image manipulation in Ruby
From: Robert Dober on 5 Jul 2010 15:12 On Mon, Jul 5, 2010 at 7:44 PM, William Rutiser <wruyahoo05(a)comcast.net> wrote: > Could you setup a mock NTP time source that supplies "fast" time to its > clients then configure each machine to use the mock NTP and update very > frequently? This may not be practical and would certainly not work if the > machines are being used for anything except your tests. I have heared that being killed by a sysadmin is a terrible fate ;) Cheers R.
From: Chuck Remes on 5 Jul 2010 16:06 On Jul 5, 2010, at 2:12 PM, Robert Dober wrote: > On Mon, Jul 5, 2010 at 7:44 PM, William Rutiser <wruyahoo05(a)comcast.net> wrote: >> Could you setup a mock NTP time source that supplies "fast" time to its >> clients then configure each machine to use the mock NTP and update very >> frequently? This may not be practical and would certainly not work if the >> machines are being used for anything except your tests. > I have heared that being killed by a sysadmin is a terrible fate ;) The idea of using a hacked NTP daemon to speed up the clocks in not feasible. Interesting idea though... cr
From: Tony Arcieri on 5 Jul 2010 16:21 [Note: parts of this message were removed to make it a legal post.] On Mon, Jul 5, 2010 at 2:06 PM, Chuck Remes <cremes.devlist(a)mac.com> wrote: > The idea of using a hacked NTP daemon to speed up the clocks in not > feasible. Interesting idea though... > Why can't the "central time" be maintained by whatever process is scattering work to your distributed nodes, and just asynchronously included in the messages for use whenever your workers get around to processing them? -- Tony Arcieri Medioh! A Kudelski Brand
From: Chuck Remes on 5 Jul 2010 17:15 On Jul 5, 2010, at 3:21 PM, Tony Arcieri wrote: > On Mon, Jul 5, 2010 at 2:06 PM, Chuck Remes <cremes.devlist(a)mac.com> wrote: > >> The idea of using a hacked NTP daemon to speed up the clocks in not >> feasible. Interesting idea though... >> > > Why can't the "central time" be maintained by whatever process is scattering > work to your distributed nodes, and just asynchronously included in the > messages for use whenever your workers get around to processing them? Because there is no centralized server that all messages, data or control must pass through. cr
From: Tony Arcieri on 6 Jul 2010 13:52
[Note: parts of this message were removed to make it a legal post.] On Mon, Jul 5, 2010 at 3:15 PM, Chuck Remes <cremes.devlist(a)mac.com> wrote: > Because there is no centralized server that all messages, data or control > must pass through. > If your system is fully asynchronous and there's no central data source, how is it possible for nodes to synchronize to a central clock? That makes absolutely no sense. -- Tony Arcieri Medioh! A Kudelski Brand |