| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

Have to add...; Culturally Liberal and Nothing More; Weird Finite / Infinite Result; Your diamond is a beaten up mess; Maths Books; Good Bike Route from Providencia / Las Condes to Panul\; Iain Pears (Author of Complex Plots); Plum Jam; Excellent; More Recently; For a moment I forgot StackOverflow sucked; A Few Weeks On...; Chilean Book Recommendations; How To Write Shared Libraries; Jenny Erpenbeck (Author); Dijkstra, Coins, Tables; Python libraries error on OpenSuse; Deserving Trump; And Smugness; McCloskey Economics Trilogy; cmocka - Mocks for C; Concept Creep (Americans); Futhark - OpenCL Language; Moved / Gone; Fan and USB issues; Burgers in Santiago; The Origin of Icosahedral Symmetry in Viruses; autoenum on PyPI; Jars Explains; Tomato Chutney v3; REST; US Elections and Gender: 24 Point Swing; PPPoE on OpenSuse Leap 42.1; SuperMicro X10SDV-TLN4F/F with Opensuse Leap 42.1; Big Data AI Could Be Very Bad Indeed....; Cornering; Postcapitalism (Paul Mason); Black Science Fiction; Git is not a CDN; Mining of Massive Data Sets; Rachel Kaadzi Ghansah; How great republics meet their end; Raspberry, Strawberry and Banana Jam; Interesting Dead Areas of Math; Later Taste; For Sale; Death By Bean; It's Good!; Tomato Chutney v2; Time ATAC MX 2 Pedals - First Impressions; Online Chilean Crafts; Intellectual Variety; Taste + Texture; Time Invariance and Gauge Symmetry; Jodorowsky; Tomato Chutney; Analysis of Support for Trump; Indian SF; TP-Link TL-WR841N DNS TCP Bug; TP-Link TL-WR841N as Wireless Bridge; Sending Email On Time; Maybe run a command; Sterile Neutrinos; Strawberry and Banana Jam; The Best Of All Possible Worlds; Kenzaburo Oe: The Changeling; Peach Jam; Taste Test; Strawberry and Raspberry Jam; flac to mp3 on OpenSuse 42.1; Also, Sebald; Kenzaburo Oe Interview; Otake (Kitani Minoru) move Black 121; Is free speech in British universities under threat?; I am actually good at computers; Was This Mansplaining?; WebFaction / LetsEncrypt / General Disappointment; Sensible Philosophy of Science; George Ellis; Misplaced Intuition and Online Communities; More Reading About Japan; Visibilty / Public Comments / Domestic Violence; Ferias de Santiago; More (Clearly Deliberate); Deleted Obit Post; And then a 50 yo male posts this...; We Have Both Kinds Of Contributors; Free Springer Books; Books on Religion; Books on Linguistics; Palestinan Electronica; Books In Anthropology; Taylor Expansions of Spacetime; Info on Juniper; Efficient Stream Processing; The Moral Character of Crypto; Hearing Aid Info; Small Success With Go!; Re: Quick message - This link is broken; Adding Reverb To The Echo Chamber; Sox Audio Tools

© 2006-2015 Andrew Cooke (site) / post authors (content).

Design Sketch for Modular Data Transfer

From: "andrew cooke" <andrew@...>

Date: Sat, 31 Mar 2007 12:02:45 -0400 (CLT)

On the plane Thursday I played around with the idea of writing a modular
system to move data (large quantities).  This is important in Astronomy at
the moment, and I'm not sure we have the best solution yet.

The approach I took was to remain as simple and modular as possible.  This
raised issues with metadata and resources.

Metadata seems unavoidable - if, for example, you are splitting files into
smaller pieces, or you want end to end verification, then you need
metadata.  And typically metadata and data have different requirements, so
tend to use different transports.  On the other hand this makes it
difficult to nest components (say you have a multi-hop transfer and want
one hop to use a component that splits data into smaller, parallel
chunks).

By "resources" I currently mean "disk space".  It should be configurable
for the system to not delete data until received at the destination (even
for multi-hops or broadcast to a known number of sinks).

The best solution I found was a hybrid approach that bundles "outgoing"
metadata with the data, but uses a separate broadcast channel for resource
release.

So during transfer the data would be packaged as a jar file (probably
uncompressed since the payload would likely already be compressed).  The
jar file would contain data and metadata (including checksums).  This
allows nesting, since a jar can contain another jar.  This has the
advantage of being "human readable" in caches and doesn't require separate
databases to associate data and metadata.

Resources are named (uniquely - probably from a naming service),
inherited, and freed on completion.  Notification is via a reliable
broadcast.  So, for example, a transfer might have two resources - the
initial resource for the data and a second resource used in an internal
hop.  If the inner resource is broadcast only that is freed, but if the
outer resource is broadcast both are freed.

I realise this is rather brief, but perhaps it will make sense to someone.
 My notes made on the plane follow.

Andrew


initial notes on file transfer toolkit


file format

uncompressed jar with MD5 and other metadata in META-INF
jars can be nested


use cases

- transfer from directory
- multi hop transfer
- several routes
- fragmentation


global reliable broadcast for resource management
global name source

intermediate data stored in temp directories (abstract to include memory?)
intermediate data are resources.

resources labelled by names.
resource can be associated with more than one resource name.
resource freed if any any resource name matches?
(generalize to boolean expression?)

directories act as queues
qos affects selection of data from directories?

initial directory unusual as name is arbitrary.
move to intermediate temp directory

final directory ditto.
populated from final temp, and then resource freed


global reliable broadcast for logging
dump to text log
ability to reconstruct history of a particular file from text log
text log human and machine readable


single-hop flow:

 +- data enters initial directory
 +- data moved to managed directory in jar format
    +- data selected from managed directory by qos
    +- data transmitted to remote target
    |  +- data arrive in remote managed directory
    |  +- data verified
    |  |  +- data unpacked into destination directory
    |  |  +- resource released
    |  +- managed data deleted
    +- managed data deleted

multi-hop could be repeated as above, but we may want to keep initial file
around.

problem with above is that file is deleted immediately from entry directory.

Storing Many Files in Directories

From: "andrew cooke" <andrew@...>

Date: Sat, 31 Mar 2007 13:12:37 -0400 (CLT)

Some interesting and informed comment related to this at
http://ask.metafilter.com/59635/Millions-of-images

So simply "using directories" is not sufficient (on many file systems).

Andrew

Comment on this post