Our great sponsors
-
We plan to use the same trick in the XVM (Ecstasy virtual machine) for its fat pointers. Each reference in Ecstasy has two conceptual pieces of information: A type and an identity. If the compiler knows that the type is fixed and the reference doesn't escape, then it can generate code knowing that type and doesn't need to encode it into the reference (assumed to be 8 bytes). Similarly, if the identity fits into the 8 bytes, then the value doesn't need to be "boxed". In our original design, for example, 8-byte ints (i.e. instances of the Int64 class) that are known to be of the type Int64 could always be stored in the fat pointer itself. We've come a long way in the design since then, but the same basic concept still holds: Don't allocate objects when the object can fit in the thing that you would have used to point to the object.
-
skybison
Discontinued Instagram's experimental performance oriented greenfield implementation of Python.
This is what we did in Skybison and it worked just fine.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
