@irongraph/node-darwin-arm64 0.1.5 → 0.1.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +15 -8
- package/THIRD_PARTY_NOTICES.txt +8902 -3
- package/irongraph.darwin-arm64.node +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,11 +1,18 @@
|
|
|
1
1
|
# IronGraph for Node.js
|
|
2
2
|
|
|
3
|
-
**Node.js access to a
|
|
3
|
+
**Node.js access to a CPU graph database with built-in streaming and queues.**
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
5
|
+
Use Cypher to query graph structure, search text and vectors, inspect property history, and
|
|
6
|
+
administer the database. Built-in Kafka-compatible Streams and AMQP-compatible Queues handle event
|
|
7
|
+
and message workloads. `@irongraph/node` provides native embedded access, remote Query API/Bolt
|
|
8
|
+
clients, and TypeScript declarations for Node.js. IronGraph is open-source software released under
|
|
9
|
+
the Apache License 2.0.
|
|
10
|
+
|
|
11
|
+
## Performance at a glance
|
|
12
|
+
|
|
13
|
+
Graph queries execute on the CPU against one shared canonical graph. Local text inference can
|
|
14
|
+
use Metal or CUDA independently. Measure complete queries separately from individual graph operations;
|
|
15
|
+
latency depends on the workload, graph size, indexes, and host.
|
|
9
16
|
|
|
10
17
|
## Database capabilities
|
|
11
18
|
|
|
@@ -101,9 +108,9 @@ Select projects explicitly with `USE` or the `projectId` argument. Each project
|
|
|
101
108
|
`KNOWLEDGE`, and `WORKSPACE` layers for source facts, curated facts, and working data. There is
|
|
102
109
|
no implicit default project.
|
|
103
110
|
|
|
104
|
-
One embedded instance owns its directory
|
|
105
|
-
|
|
106
|
-
|
|
111
|
+
One embedded instance owns its directory. Graph execution uses one shared CPU graph; text inference
|
|
112
|
+
selects its device independently. CUDA text inference requires a CUDA-enabled release. Parallel reads
|
|
113
|
+
do not wait for writers and may observe mixed values during a multi-record write. IronGraph embeds text
|
|
107
114
|
locally and does not run generative language models.
|
|
108
115
|
|
|
109
116
|
Use `Client.apiMtls` or `Client.boltMtls` for remote access with certificate, private-key, and
|