Wannes Rombouts wapiflapi

## binglide2_ipc.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                wapiflapi
                / binglide2_ipc.md
            
            
              Last active
              August 29, 2015 14:15
            
              
                IPC architecture for binglide V2
              
          
    OUTDATED

This document is now outdated, thanks for the feedback everyone.
This is basically what I will be trying out next:

The rest of this document is available for reference.

Goals


## granularity.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                wapiflapi
                / granularity.md
            
            
              Created
              February 11, 2015 16:30
            
              
                Notes about binglide v2 architecture
              
          
    Remarks about distributed computing.


Right now we have the need to compute histogram data on large files with
cache support. This can work great by having a reducer process agregating
results from mappers. this works because we have one type of reducer and one
type of mapper with a minimum map/reduce ratio among the workers.


What happens if in the future we need something like A <- B <- C. This will
require at least three processes with two of them waiting. We need to make


## binglide2_ipc2.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                wapiflapi
                / binglide2_ipc2.md
            
            
              Created
              February 16, 2015 00:10
            
              
                More ramnling about binglide's IPC architecture
              
          
    The purpose of this document is to explain the design decisions being taken for
the multiprocessing and IPC architecture of binglide v2.
Synopsis

The main idea that this document ends up advocating is to have N workers for
each type of service. In this scenario each worker knows how to do only one
task. Those workers receive tasks from the broker who is responsable for
splitting jobs into smaller tasks accoring to the cache. This endsup being hard

  
## broker.py
#!/usr/bin/env python3
# -*- coding: utf-8 -*-

import collections

import zmq

import ipc


## venv
#!/bin/sh

source ./venv/bin/activate
"$@"

## req.gql
{
  repositoryOwner(login: "github") {
    login
    avatarUrl
    repositories(first: 10, isFork: false,  orderBy: {field: CREATED_AT, direction: DESC}) {
      edges {
        node {
          description
          createdAt
          stargazers {

## tracing.py
from graphql.execution import ExecutionResult

from .schema import schema

import datetime
import dateutil.parser
import dateutil.tz

import monotonic

## fish_prompt.fish
# name: wapiflapi

function _git_branch_name
  command git symbolic-ref HEAD ^/dev/null | sed -e 's|^refs/heads/||'
end

function _git_repo_name
  basename (git rev-parse --show-toplevel ^/dev/null) ^/dev/null
end

## sss.html
<!DOCTYPE html>
<html lang="en">
    <head><title>Self Share Screen</title></head>
    <body><video id="video" autoplay></video></body>
    <script>
     navigator.mediaDevices.getDisplayMedia({
         video: { cursor: "never" },
         audio: false
     }).then(function (stream) {
         document.getElementById("video").srcObject = stream;

## gist:e7674d1a889aced8fd1189c4f9902b02
# @wapiflapi gqldl early draft.
#
# The goal of this is to manage dataloaders for multiple types while
# at the same time providing an easy integration for relay-compliance.
#   - There will be full utility support for the relay spec.
#   - Integration with ariadne WILL be easy and documented.
#   - Integration with graphene MIGHT be documented.
#
# Feel free to comment, but documentation, tests and a proper release
# are comming soon(tm).
	#!/usr/bin/env python3
	# -- coding: utf-8 --

	import collections

	import zmq

	import ipc
	{
	repositoryOwner(login: "github") {
	login
	avatarUrl
	repositories(first: 10, isFork: false, orderBy: {field: CREATED_AT, direction: DESC}) {
	edges {
	node {
	description
	createdAt
	stargazers {
	from graphql.execution import ExecutionResult

	from .schema import schema

	import datetime
	import dateutil.parser
	import dateutil.tz

	import monotonic
	# name: wapiflapi

	function _git_branch_name
	command git symbolic-ref HEAD ^/dev/null \| sed -e 's\|^refs/heads/\|\|'
	end

	function _git_repo_name
	basename (git rev-parse --show-toplevel ^/dev/null) ^/dev/null
	end
	<!DOCTYPE html>
	<html lang="en">
	<head><title>Self Share Screen</title></head>
	<body><video id="video" autoplay></video></body>
	<script>
	navigator.mediaDevices.getDisplayMedia({
	video: { cursor: "never" },
	audio: false
	}).then(function (stream) {
	document.getElementById("video").srcObject = stream;
	# @wapiflapi gqldl early draft.
	#
	# The goal of this is to manage dataloaders for multiple types while
	# at the same time providing an easy integration for relay-compliance.
	# - There will be full utility support for the relay spec.
	# - Integration with ariadne WILL be easy and documented.
	# - Integration with graphene MIGHT be documented.
	#
	# Feel free to comment, but documentation, tests and a proper release
	# are comming soon(tm).