Skip to main content
benchmarkedInspired by Biological neuron spike trains

Spike-Timed Event Log

Counterpart to Payload-heavy event logs (JSON logs, structured logging)

Key Properties

  • O(1) amortized ingest with 17-81 byte events (26-48x compression vs JSON logs)
  • Real-time pattern classification via streaming ISI analysis (Tonic, Burst, Accelerating, Decaying, Silent, Irregular)
  • Pre-computed rate counters with O(1) dashboard queries
  • Population-aware correlation: synchrony detection, burst analysis, N-of-M integration
  • Segmented append-only storage with sparse stream indexing
  • Refractory period enforcement prevents ingestion flooding

Operation Complexity

Side-by-side comparison with the classical counterpart.

Operation complexity comparison
OperationSpike-Timed Event LogPayload-heavy event logs (JSON logs, structured logging)
ingestO(1) amortizedO(1) amortized
rate queryO(1)O(n) or pre-aggregated
pattern classificationO(1) streamingN/A
population correlationO(streams)N/A
space per event17-81 bytes200-2000 bytes

Interface Preview

spike_timed_event_log.rs
rust
1pub struct SpikeStore { /* ... */ }
2
3impl SpikeStore {
4    pub fn new(config: SpikeStoreConfig) -> Self;
5    pub fn from_preset(preset: SpikePreset) -> Self;
6
7    // Tag registration
8    pub fn register_tags(&mut self, tags: &[(String, String)]) -> u64;
9
10    // Ingestion
11    pub fn ingest_presence(&mut self, tag_hash: u64, timestamp_ns: u64) -> Result<(), SpikeError>;
12
13    // Statistics
14    pub fn stats(&self) -> &StoreStats;
15}
16
spike_timed_event_log.ts
typescript
1class SpikeStore {
2  async init(): Promise<SpikeStore>;
3
4  // Tag registration
5  registerTag(key: string, value: string): number;
6
7  // Ingestion
8  ingestPresence(tagHash: number, timestampNs: number): void;
9
10  // Statistics
11  readonly totalEvents: number;
12  readonly totalTransitions: number;
13}
14

Where This Matters

Datadog / Splunk

Log Ingestion Pipeline

Improvement comparison
TodayWith Spike-Timed Event LogHow
200-2000 byte structured log entries17-81 byte spike eventsPresence-class encoding; temporal pattern is the payload
Post-hoc pattern analysis (regex, ML)Real-time 6-class pattern classificationStreaming ISI analysis classifies patterns during ingest
Rate dashboards require pre-aggregation pipelinesO(1) rate queries from pre-computed windowsSliding rate counters maintained inline during ingest

Interactive Simulation

Simulation coming soon

An interactive visualization of Spike-Timed Event Log behavior will be available here.

View all simulations

Discussion

Questions, ideas, or experiences with Spike-Timed Event Log? Join the discussion.