Skip to content

Performance ​

These numbers come from a test suite that runs the real tallymoth program and talks to it over HTTP. They are updated for every release. The tables are written by the suite, so do not edit them by hand. To run it yourself, see Testing and benchmarks.

Read the numbers as a guide

Everything ran on one 4-core desktop, and the load generator ran on the same machine as the server, so the two shared the CPU. A server with its own cores will do better. What carries over to other machines is the pattern: what is fast, what slows down, and where the limits are.

The short version ​

  • Writing: about 30,000 events per second for each CPU, up to 2 CPUs.
  • Hourly count queries (what most charts need) take 1 to 4 ms, even with 10 million events.
  • Filter and average queries read every event, so they take about 1 second per million events. With 10 million events they time out.
  • Reading does not slow writing, and writing does not slow reading much.
  • Memory: 128 MB is enough. The server itself used under 80 MB. At 64 MB it was killed.
  • Disk: about 150 bytes per event.

Latest results ​

Measured on tallymoth 0.1.0-dev on 2026-11-14. Intel Core i5-6600 @ 3.30GHz, 4 cores, linux/amd64. 8 clients sending batches of 20 events, 10 seconds per test.

What we measuredResult
Events accepted per second, bearer key38,915
Events accepted per second, signed requests40,448
Hourly count query, 1,000,000 events stored4.0 ms
Filter or average query, 1,000,000 events stored1.2 s
Hourly count query while writing at full speed17 ms
Memory used, idle and at peak12 MB and 67 MB
Disk space per event149 bytes
Every query we timed
QueryAnswered fromTypical timeSlow end (p95)
count per day, 30 dayssummary table1.1 ms1.4 ms
count per hour, 7 dayssummary table1.0 ms1.5 ms
count per day by os, 30 dayssummary table4.0 ms5.3 ms
count per hour by os, 7 dayssummary table2.9 ms3.6 ms
count per day, filtered (where)all events in range946.9 ms1075.5 ms
average cores per dayall events in range1161.0 ms1303.8 ms
count per 15 min, 1 dayall events in range8.3 ms10.3 ms

Write requests with a bearer key took 1.2 ms typically and 4.7 ms at the slow end. Under this load 28317 requests were told to slow down (503) and 0 failed otherwise.

Different servers and different amounts of data ​

Each table answers one question.

How many events per second, with different CPUs? ​

CPUs given to the serverEvents accepted per secondHourly count query while writing
0.517,19094 ms
132,52163 ms
254,94929 ms
441,66715 ms

How much memory does it need? ​

Memory limitResultMemory used at peak
64MBKilled: ran out of memory31 MB
128MBWorks76 MB
256MBWorks74 MB
512MBWorks75 MB
1GBWorks73 MB

How does it slow down as data grows? ​

Events storedDisk spaceHourly count queryFilter or average query
100,00017 MB3.9 ms109 ms
1,000,000142 MB3.8 ms1.2 s
5,000,000700 MB3.8 ms6.1 s
10,000,0001401 MB3.8 mstimed out (over 8 s)

What the words mean ​

  • Events accepted per second counts only events the server took. When the clients send faster than the disk can save, the server answers 503 ("slow down") instead of piling up work in memory. That is normal, and well-behaved clients wait and try again.
  • Hourly count query is a count with steps of one hour or more. It reads a small summary table, so its time depends on how many hours and values are in the answer, not on how many events exist.
  • Filter or average query is a where, sum, avg, min or max. It reads every event in the time range. See Query API: Speed.
  • Timed out means the query took longer than the server's 8 second limit and failed.
  • Memory used at peak is the most memory Docker reported for the container, checked about once a second. A server run directly on a host shows a bigger number, because database pages mapped into memory count there, even though the system can take them back.
  • Killed: ran out of memory means the container went over its limit and was stopped. The tests after that fail. We did not look into why 64 MB is too small.

Planning a server ​

WhatRule of thumb
Diskabout 150 bytes per event. 1 million events a day is about 150 MB a day, minus what retention deletes.
Example50,000 events a day kept for 180 days is about 9 million events, or 1.3 GB.
MemoryGive it 128 MB. It used 12 MB idle and under 80 MB under load.
CPUAbout 30,000 events per second for each CPU, up to 2 CPUs. Most apps need far less.
Slow queriesKeep filter and average queries to ranges under about 5 million events.

History ​

One row for each release: events accepted per second, how long an hourly count query takes, the same query while writing at full speed, and peak memory.

VersionDateEvents per second (bearer)Events per second (signed)Hourly count queryHourly count query while writingPeak memory
0.1.0-dev2026-11-1438,91540,4484.0 ms16.7 ms67 MB

Released under the MIT License.