On Wed, Jul 29, 2020 at 11:40 AM Ben Goertzel <[email protected]> wrote:
>
> have three different statuses: Local, Remote (in RAM on some other
> machine in Distributed Atomspace) or BackedUp (disk).
The distinctions between these can become rather blurry. The point of
disk-backup is to not lose data, but if your data is in RAM on a remote
server, that might be enough. High-end database machines have
battery-backed disk drives, so that a powerloss to the building does not
lose in-flight transactional data.
Compute centers often have waterfalls of 100-gigabit optical fibers
splashing out the back of the CPU's, going to the far end of the room, and
attaching to RAM and/or disks there -- this is not new; in 1995, the
infiniband storage interconnect ran tcp/ip to disk-drives and allowed
remote-DMA access to RAM. The now-defunct blue-rivers had fiber-optics
going straight into the CPU chip itself, because this used less power than
toggling electrical bits on a metal pin, thus saving on power and cooling.
But it also meant that the RAM could be as far away as your fiber-optic
cable is long. The commercial storage market has some really wild stuff
out there that addresses common issues faced by the market. The
local/remote/backed-up distinction is a heritage of 1960's-1990's tech and
consumer-grade hardware. It's not a bad distinction, it's just .. blurry,
slightly archaic, rapidly-changing and we don't want to bake it into any
AtomSpace specifications.
-- Linas
--
Verbogeny is one of the pleasurettes of a creatific thinkerizer.
--Peter da Silva
--
You received this message because you are subscribed to the Google Groups
"opencog" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/opencog/CAHrUA36Vhn-zFqizu6srMJ_gVbQttqt8jG-%2BOr1emD1c70X_LQ%40mail.gmail.com.
