This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-07
Channels
- # aleph (3)
- # aws (7)
- # beginners (117)
- # boot (119)
- # cider (2)
- # cljs-dev (3)
- # clojure (193)
- # clojure-austin (1)
- # clojure-dusseldorf (4)
- # clojure-finland (5)
- # clojure-france (5)
- # clojure-italy (7)
- # clojure-portugal (1)
- # clojure-russia (204)
- # clojure-serbia (5)
- # clojure-spec (31)
- # clojure-uk (64)
- # clojurescript (288)
- # community-development (9)
- # core-async (54)
- # cursive (8)
- # datascript (18)
- # datomic (26)
- # dirac (8)
- # emacs (26)
- # figwheel (1)
- # hoplon (16)
- # jobs (2)
- # jobs-discuss (4)
- # juxt (1)
- # lein-figwheel (4)
- # leiningen (14)
- # london-clojurians (2)
- # lumo (17)
- # off-topic (44)
- # om (63)
- # om-next (2)
- # onyx (26)
- # perun (14)
- # planck (5)
- # portland-or (34)
- # proton (2)
- # protorepl (8)
- # quil (1)
- # re-frame (6)
- # reagent (16)
- # remote-jobs (4)
- # ring (7)
- # ring-swagger (10)
- # rum (1)
- # untangled (2)
@conaw what are you putting in the value of each datom?
let’s say at least 1/2 of them are db/refs to other datoms, and half are strings that are about a paragraph in length
well then yeah, i'd say your talking many millions for 100MB of memory
you could test it pretty easy
@tonsky do you think a datascript app would perform comfortably well with many millions of datoms? Has anyone seen this in the wild?
just transact a bunch of data into a db
from my experience (with far less than millions of datoms) you'll get different perf characteristics with the different APIs exposed by datascript
e.g. queries vs pull vs datoms
but i don't know how they scale differently
i'd assume, for instance, that the query building part of running a query doesn't change with additional datoms
just try it out 🙂
pragmatically speaking though, you're probably not going to be rendering and updating millions of DOM elements