You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Wrap your untrusted NIFs so that they can never crash your node.
20
20
21
21
## Benchmarks
22
22
23
-
Benchmarks can be found in the [`bench`](./bench/) directory. As of v0.1.0, SafeNIF has not implemented pooling of peer nodes.
23
+
Benchmarks can be found in the `bench` directory. As of v0.1.0, SafeNIF has not implemented pooling of peer nodes.
24
24
This means that it currently incurs the high cost of starting up a peer node for every call, which can take anywhere from 100ms to over a second,
25
25
depending on how much code needs to be loaded onto the peer node. You can see from the benchmarks that out of the three methods benchmarked (CLI+Port, NIF, SafeNIF),
26
26
SafeNIF is currently the slowest due to this incurred cost.
0 commit comments