mikaelronstrom

5 ms·

1.
Scalable Revisioned Graph Database(blog.dydra.com)
1 points by mikaelronstrom 1y ago|1 comments
2.
by mikaelronstrom 1y ago
Dydra using RonDB as backend scales to many billions of items in a graph database with revisioned history.
3.
by mikaelronstrom 1y ago
Not sure how it is today, but in the 90s and early 00s when I worked at Ericsson Mnesia had a number of systems that it was used in. There was interestingly 4 DBMSs developed at Ericsson in the 90s and 00s. Mnesia and NDB Cluster as mention
4.
How to design a DBMS for Telco requirements(mikaelronstrom.blogspot.com)
33 points by mikaelronstrom 1y ago|4 comments
5.
How to reach 100M Key lookups using REST server with Python clients(mikaelronstrom.blogspot.com)
1 points by mikaelronstrom 1y ago|1 comments
6.
by mikaelronstrom 1y ago
This provides the How-To explanation of challenges one can meet when building highly scalable Key-value stores using a REST server and Python clients.
7.
100M Key Lookups/SEC with REST API and Python(rondb.com)
1 points by mikaelronstrom 1y ago|0 comments
8.
by mikaelronstrom 2y ago
The reliability of OVH has so far not been a problem. Performance is mostly a factor of the VM instances that you use, AWS has much more instances to choose from, but obviously at a much higher cost, so performance per dollar is obviously b
9.
by mikaelronstrom 2y ago
There are lots of alternatives for database solutions with Kubernetes, in Hopsworks we use RonDB which is highly available and has a MySQL interface but also supports a REST API and even a prototype Redis service.
10.
by mikaelronstrom 2y ago
One obvious benefit of OVH compared to Hetzner is the S3 storage, the Kubernetes framework and a number of other services provided by OVH, don't think Hetzner would provide those services.
11.
by mikaelronstrom 2y ago
Hopsworks has a platform with a high-availability database (RonDB), a highly available distributed file system (HopsFS) and the services are also redundant. Hopsworks even supports failover to another region. So the software is very reliabl
12.
by mikaelronstrom 2y ago
Intriguingly simple implementation of fibers in Linux and Mac OS X can be used to experiment on the use of fibers in the RonDB database engine.
13.
by mikaelronstrom 3y ago
New VM types using Intel/AMD VMs of the 4th generation in GCP is compared to 2nd generation VMs. Benchmark is Sysbench and database is RonDB (www.rondb.com).
14.
by mikaelronstrom 3y ago
Some playing with numbers for vacations.
15.
by mikaelronstrom 3y ago
RonDB is a KV store with SQL capabilities (the MySQL storage engine NDB is maintained by Oracle as part of MySQL NDB Cluster). Hopsworks is on top of this adding a new REST API (REST + gRPC) service that is already in the github tree and wi
16.
The return of Desktops for development environment(mikaelronstrom.blogspot.com)
1 points by mikaelronstrom 4y ago|1 comments
17.
by mikaelronstrom 4y ago
Most developers today use laptops for all development work. For the last 15 years I have considered desktops and laptops to be very similar in performance and use cases. This is no longer the case as I will discuss in this blog.
18.
by mikaelronstrom 4y ago
LATS stands for low Latency, high Availability, high Throughput and scalable Storage. When testing an OLTP DBMS it is important to look at all those aspects. This means that the benchmark should test how the DBMS works in scenarios where d
19.
RonDB receives ARM64 support and large transaction support(mikaelronstrom.blogspot.com)
2 points by mikaelronstrom 5y ago|0 comments
20.
Automatic memory management in RonDB(mikaelronstrom.blogspot.com)
14 points by mikaelronstrom 5y ago|1 comments
21.
by mikaelronstrom 5y ago
After 5 years of development all steps in the new memory management architecture in RonDB is completed. This has been introduced in 4 steps and now the final step is completed. Thus it is a good time to describe the architecture and how it
22.
by mikaelronstrom 5y ago
General optimisations are not so common to work on, but new HW requires new thinking about database architecture. A few examples, Scaling to more CPU cores, Scaling to bigger RAM, bigger disks, scaling to larger systems. Introduction of new
23.
Ha vs. AlwaysOn(mikaelronstrom.blogspot.com)
4 points by mikaelronstrom 5y ago|1 comments
24.
by mikaelronstrom 5y ago
Regarding memory a very quick formula (more details exists in docs.rondb.com and in blogs) is around 25 bytes of overhead per row plus 15 bytes of overhead per primary key index and an additional 10 bytes per row per ordered index. Non-inde
25.
by mikaelronstrom 5y ago
RonDB Community is GPL v2 and there is no limitations to its use. Our business model is to provide the managed service of operating RonDB and providing support for that.
26.
by mikaelronstrom 5y ago
RonDB have an interpreter that can execute a set of simple things. It is mostly used to push filtering, to push increments/decrements. There is also a pushdown join processor in it. It wouldn't be very hard to build more functiona
27.
by mikaelronstrom 5y ago
RonDB has the capabilities to both scale on VM size and number of VMs as online operations. The auto part requires that we support in the managed version as well. Hopsworks have added auto-scaling to AI worker nodes. So auto-scaling in RonD
28.
by mikaelronstrom 5y ago
Yep, this is a key difference between traditional SQL databases and key-value databases. SQL databases optimise specific queries and have a high overhead per query. Key-value databases have a low overhead per query and optimise on flows of
29.
by mikaelronstrom 5y ago
For the moment managed RonDB will provide the availability of the cloud, but remember that the managed version is still in development. The steps to go 6 9s requires 1) Integrate cloud APIs such that we know when the cloud provider will fre
30.
by mikaelronstrom 5y ago
Correct, Availability is the amount of time you are available to read and write data. Durability is the amount of time your data is not lost. The metrics mentioned in this post are about availability. Most cloud vendors provide SLAs of 99.9

More ›