zh217

11 ms·

31.
ChatGLM, a ChatGPT-like LLM developed by Tsinghua Univ, runnable on consumer GPU(chatglm-cn.translate.goog)
5 points by zh217 4y ago|1 comments
32.
by zh217 4y ago
The project description is in Chinese, so I've used the Google translate URL for this submission. The GitHub page for the project is https://github.com/THUDM/ChatGLM-6B I've tried the model on my own machine,
33.
by zh217 4y ago
Another problem with Clojure-based Datalog is performance. Yet another is you are pretty much tied to the Clojure ecosystem. And I don't really like the Clojure-fused Datalog syntax either. These pains spurred me to write my own: http
34.
by zh217 4y ago
I spent ten minutes reading this and lost interest. Everything he explains in the beginning of this article is obvious or common sense (common sense for anyone who has a physics degree, that is) and I am not sure where the "new" t
35.
Cozo 0.5: the versatile embeddable graph database with Datalog is half-way 1.0(github.com)
1 points by zh217 4y ago|0 comments
36.
by zh217 4y ago
I think you should try Datalog, or a flavour of it called Cozo: https://docs.cozodb.org/en/latest/ Disclaimer: I wrote Cozo.
37.
Time travel in a database: a Cozo story(docs.cozodb.org)
1 points by zh217 4y ago|0 comments
38.
Cozo is a performant graph database that runs everywhere(github.com)
2 points by zh217 4y ago|0 comments
39.
by zh217 4y ago
What you described can be implemented efficiently with B-trees. The problem is, the required operation is low-level and not usually exposed by the database engines. Basically you need to be able to walk the tree, up and down. Say your table
40.
by zh217 4y ago
More precisely, Cozo currently has a RocksDB backend. The development version also has SQLite backend (for easier compilation on mobile platforms), in-memory backend, etc. It now can run as a web assembly module as well (see https:/&#
41.
by zh217 4y ago
Around 10 GBs of data, on the standalone version. We will have systematic benchmarks when the API, syntax, etc. settle down a little bit.
42.
by zh217 4y ago
Yes. For example, in Postgres you can sort tables arbitrarily large, not constrained by main memory. Postgres uses external merge sort when the tables are really large. There are other situations where the working data are disk-based when t
43.
by zh217 4y ago
Technically, Cozo is using something called "Datalog with stratified negation, stratified aggregation, and function symbols", allowing aggregations to be auto-recursive when they form a semi-lattice, together with built-in algorit
44.
by zh217 4y ago
I believe you are referring to Datomic's pull syntax ( https://docs.datomic.com/on-prem/query/pull.html ). The way I see it is that this is an add-on to the query language, not a core part of it, since it appli
45.
by zh217 4y ago
Differential-datalog is a cool project. I think the targeted use cases are different as compared to Cozo. The most important difference is that Cozo is focused on graphs, whereas differential-datalog is focused on incremental computation. T
46.
by zh217 4y ago
Re Datalog syntax: yes, the "composability" is the main reason that I decided to adopt it as the query language. This is also the reason why we made storing query results back into the database very easy (no pre-declaration of &qu
47.
by zh217 4y ago
Thanks for your interest in this! It currently uses RocksDB as the storage engine. If your server has enough resources, I believe it can store TBs of data with no problem. Running queries on datasets this big is a complicated story. Point l
48.
by zh217 4y ago
I realized my mistake, as I said in the other comments. The main repo is now under LGPL. I'll see what I'll do with the bindings. Writing code is so much better than dealing with licenses!
49.
by zh217 4y ago
OP here. Nothing about the license is final yet since there are no outside contributors. I just changed the main repo to LGPL, not because what I believed in changed, but because it seems that I really misunderstood the licenses.
50.
by zh217 4y ago
It seems that I really did misunderstand the differences. It is now under LGPL. The repo still requires CLA for contribution for the moment until I am really sure.
51.
by zh217 4y ago
Thank you for your perspective. Maybe I was confused about the case of using an executable vs linking against a library. Let me double-check with a few friends who understand copyright laws better than me. If everything checks out, the next
52.
by zh217 4y ago
Maybe, and maybe I need to consult a lawyer someday to get the facts straight. To tell you the truth my head hurts when I attempt to understand what these licenses say. Regardless, I intend this project to be true FOSS, the "finer deta
53.
by zh217 4y ago
No, my understanding is that if you don't make any changes to the Cozo code, you don't need to release anything to the public. If you do, and you cannot release your non-Cozo code, then you must dynamically link to the library (an
54.
by zh217 4y ago
I find nothing wrong with the classical syntax, but there is a very practical, even stupid reason why the syntax is the way it is now. As you can see from the tutorial ( https://nbviewer.org/github/cozodb/cozo-docs&
55.
by zh217 4y ago
My use of "embedded" means that the whole database runs in the same process as your application. This is how SQLite works. Your application doesn't "connect" to an SQLite database in the usual sense. Your applicatio
56.
by zh217 4y ago
Yes of course. Perhaps I should start by clarifying that I am talking about the number of queries the Cypher language can express, without any vendor-specific extensions, since my consideration was whether to use it as the query language fo
57.
by zh217 4y ago
Transactions are described in the manual: https://cozodb.github.io/current/manual/stored.html#chaining... . Sorry about the docs being all over the place at the moment! My only excuse is that Cozo is very young. Th
58.
by zh217 4y ago
In short: yes, but not right now. See this issue: https://github.com/cozodb/cozo/issues/2 . Also in this case you are not really using it as an embedded database anymore, which is our original motivation. We c
59.
by zh217 4y ago
For the moment: you can have as much data as you want on disk as long as the RocksDB storage engine can handle it, which I believe is quite large. For any single query though, you want all the data you touch to fit in memory. The good news
60.
by zh217 4y ago
It's actually quite normal for experimental and observational subjects, which is the case for this one. I believe the record is set by one with over 5000 authors - see https://www.nature.com/articles/nature.2015.17

More ›