God orgen

gd mrgn

gd mrn

g m

m

Jeg endra min melding til å passe inn i vitsen

jeg hadde egentlig en South Park-vits i hodet, men bomma 😂 Tenkte på han fyren som ikke kan si “t”-en i “Planetarium”. Men jeg utelot to bokstaver.

Nå erre snart ferie, si

har sett noen nydelige klipp fra nyere episoder av South Park, må begynne å se på South Park igjen

Ja, jeg har falt av

dette er South Park akkurat sånn det skal være https://www.youtube.com/watch?v=2N8_5LDkZwY

😂

> You’ve lived a life with the royal family, and have had everything handed to you, but you say your life has been hard?

😆

Jeg limer inn et svar fra en tråd her, hvor @terjesb har noe spennende nytt om Datomic (i hvert fall for meg) 🙂 https://clojurians.slack.com/archives/C061XGG1W/p1680687328890689?thread_ts=1680259235.513559&cid=C061XGG1W

This might be useful for the whole channel. @slipset you can also read directly https://github.com/ardoq/architecture-decision-records/blob/main/decisions/0004-replace-mongodb-with-postgresql.md#o2-datomic > Multi-tenancy: ❌✅ - a single DB instance can host multiple databases BUT this only works well in Datomic Cloud and not really in on-prem, since all the DBs contend for the same limited resources - “there are operational considerations making it a poor fit”. The only feasible solution in on-prem is 1 transactor per DB and thus $5k per DB per year. In Cloud can have 100s to thousands of separate DBs. > … > From Datomic Support (Jaret Binford, 28/9) on the infeasibility on using on-prem with multiple databases: > The quick and dirty: Multi-tenancy in on-prem is a no-go. There is not an enforced limit on DBs in on-prem but there are operational considerations making it a poor fit. Chiefly because the transactor was designed to serve a single primary DB (some small secondary DBs are OK for operations type tasks), but the transactor has to hold in memory the sum of each DB’s memory index. With large enough DBs this becomes a resource problem. Furthermore there are no per DB stats in Datomic on prem, all DBs compete for space in the object cache, queries and transactions compete for CPUs and garbage collection pauses have impact across all DBs. You can certainly run multiple DBs, but I recommend that any mission-critical DB have their own dedicated transactor and peer processes. > Multi-tenancy in Cloud is fully supported and you can have 100s to thousands of separate DBs on a Datomic cloud system. There are still operational impacts to having so many DBs but you can scale compute nodes to optimize performance, utilize query groups to offload read per DB and have the ability to scale. The answer to https://forum.datomic.com/t/large-number-of-database/1038 > Generally, I would consider a multi-tenancy of 10 or so databases to likely be fine, with as many as a fifty or a hundred if they’re quite small and infrequently used. seems to be not fully consistent with the previous one, which claims 100s - 1000s could be fine. So perhaps Cognitect does not know itself 😭