You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Elixir benchmark of different implementations of the 'subarray sum' problem
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Building an LXD 3-node Cluster on DigitalOcean with a ZFS storage based pool and
FAN networking enabled.
In this example i'm using a Ubuntu 22.04 vainilla image with a 20GB extra volume disk attached to each droplet to be used for a ZFS storage pool. This ZFS pool will be named "local" and can be later expanded online by adding more physical volumes to the nodes. The 3 nodes are orion, rigel and vega, the first one used as the leader node in the cluster and the others as secondary nodes.The LXD version used is 5.15.
A FAN network is also configured for the potential containers that will run in the LXD cluster. if you dont know what is a FAN network please check here: https://wiki.ubuntu.com/FanNetworking
First we create 3 droplets on DigitalOcean's control panel, as this is the minimum number for quorum in the cluster and each with a 20GB unformatted volume attached, all in the same region and using same VPC.
Next we install LXD and ZFS-utils on all droplets:
There are a wide variety of machines that can be described as "stack-based" or "register-based", but not all of them are practical. And there are a lot of other decisions that affect that practicality (do variables have names or only address/indexes? fixed-width or variable-width instructions? are you interpreting the bytecode (and if so, are you using machine stack frames?) or turning it into machine code? how many registers are there, and how many are special? how do you represent multiple types of variable? how many scopes are there(various kinds of global, local, member, ...)? how much effort/complexity can you afford to put into your machine? etc.)
Elixir runtime-controlled supervision tree using feature flags (circuit breaker)
These snippets provide a foundation for starting and stopping supervision trees at runtime using feature flags (e.g. Launch Darkly).
Some things to note when adapting these snippets:
application.ex needs to be adapted into an existing application. The important part is that each child spec provided is compliant, and that there is a feature flag (ld_key) specified.
As written, if a feature flag fails for some reason, it defaults to starting all children. There is room for adaptation here as needed.
This implementation will still require a FeatureFlags module to be available that implements is_on?/2. Adjust as needed to accomodate your own feature flag setup.
What do Tensorflow, Apache Airflow, Rule Engines, and Excel have in common?
Under the hood they all use DAGs to model data-flow dependencies of the program. Using graphs to model programs is great because you can modify the program at runtime. Lets talk about doing this in Elixir for great good.
In file included from /home/wasmedge/sel4_wasmedge/build/include/c++/v1/unordered_map:435,
from /home/wasmedge/sel4_wasmedge/projects/wasmedge/include/common/enum_configure.h:19,
from /home/wasmedge/sel4_wasmedge/projects/wasmedge/include/common/configure.h:15,
from /home/wasmedge/sel4_wasmedge/projects/wasmedge/include/ast/instruction.h:18,
from /home/wasmedge/sel4_wasmedge/projects/wasmedge/lib/interpreter/engine/engine.cpp:2:
/home/wasmedge/sel4_wasmedge/build/include/c++/v1/__hash_table:2069:1: warning: always_inline function might not be inlinable [-Wattributes]
2069 | __hash_table<_Tp, _Hash, _Equal, _Alloc>::__emplace_unique_key_args(_Key const& __k, _Args&&... __args)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/wasmedge/sel4_wasmedge/build/include/c++/v1/__hash_table:2069:1: warning: always_inline function might not be inlinable [-Wattributes]
Exercise in container image saving, loading from file, and embedding as compressed base64 encoded text string
Container image file and transportation
Conclusion:
Images can be saved to file or base64 encoded for building directly into golang binaries, python/bash scripts, and carrying independently across disconnected systems.
Unfortunately, the only way to preserve image metadata is to save as a docker-archive transport type, and to podman load the resulting archive via following step: