@elaraai/east-c-cli 1.0.85 → 1.0.87

package/README.md

@@ -104,14 +104,33 @@ gone.
 
 ```bash
 east-c run task.beast2 -i rows.beast2 --profile
+east-c exec unit.beast2 --profile
+EAST_PROFILE=1 EAST_PROFILE_INTERVAL=300 east-c exec unit.beast2
 ```
 
-prints every East function the run called, by self time, with its call
-count, its total time, and where it is: the name of the Let it was bound to
-when the IR has one, its definition site, and — when that differs — the
-site of the first call that reached it, which is what tells apart helpers
-the TypeScript builder inlined at their call sites. Off, profiling costs
-one branch per call.
+prints, after the work (and after a failure's error), every East function
+and platform function it called, by self time, with its call count, its
+total time, and where it is: the name of the Let it was bound to when the
+IR has one, its definition site, and — when that differs — the site of the
+first call that reached it, which is what tells apart helpers a builder
+lowered to calls at their call sites. A platform function is an entry of
+its own, named after it and placed by the call that reached it, so the time
+spent inside it is not its caller's self time. So is a lazily read input's
+decoding: each segment its reads decode, and its whole decode when an
+operation the pager cannot serve needs one, is a call of one entry named
+after the input as `-v` names it (`input 1`), placed by the first read that
+decoded. Keyed reads at random beyond the segments the pager keeps
+(`EAST_PAGED_CACHE_BYTES`), or a scan repeated, show there; the reading
+function's total time keeps those decodes, and its self time does not.
+
+`EAST_PROFILE` set to anything but `0` profiles without the flag, which is
+how a task run by e3 is profiled: e3 hands its environment to the runner,
+and the report lands in the task's log. `EAST_PROFILE_INTERVAL=N` (seconds)
+also prints the profile so far every N seconds while the work runs, a call
+still under way counted with its time so far; an interval that is not a
+number of seconds is said and ignored. east-py's runner prints the same
+report (the profiler is libeast-c's). Off, profiling costs one branch per
+call.
 
 The `ir` toolbox (issue #627) works on IR files without running them:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elaraai/east-c-cli",
-  "version": "1.0.85",
+  "version": "1.0.87",
   "description": "Provides the `east-c` bin. A tiny launcher resolves the native binary for your platform from the matching per-platform package (@elaraai/east-c-cli-<target>), pulled in via optional dependencies.",
   "bin": {
     "east-c": "bin/east-c.mjs"
@@ -32,14 +32,14 @@
     "node": ">=18.0.0"
   },
   "devDependencies": {
-    "@elaraai/east": "1.0.85"
+    "@elaraai/east": "1.0.87"
   },
   "optionalDependencies": {
-    "@elaraai/east-c-cli-linux-x64": "1.0.85",
-    "@elaraai/east-c-cli-linux-arm64": "1.0.85",
-    "@elaraai/east-c-cli-darwin-arm64": "1.0.85",
-    "@elaraai/east-c-cli-darwin-x64": "1.0.85",
-    "@elaraai/east-c-cli-win32-x64": "1.0.85"
+    "@elaraai/east-c-cli-linux-x64": "1.0.87",
+    "@elaraai/east-c-cli-linux-arm64": "1.0.87",
+    "@elaraai/east-c-cli-darwin-arm64": "1.0.87",
+    "@elaraai/east-c-cli-darwin-x64": "1.0.87",
+    "@elaraai/east-c-cli-win32-x64": "1.0.87"
   },
   "scripts": {}
 }