PDX Python Meetup
Delicious data with mmstats
- You have an app.
- It has state.
- What is my app doing?
- How do you inspect for that state?
- Simple in-memory stats get hard to expose in multi-process environments.
- Universally supported
- Easily enhanced
- Libraries suck
- Operational burden (rotating, shipping, routing, etc)
- Records events more than inspects state
- Difficult to predict where needed
- Performance impact if too verbose
- Fast, sexy, "enterprise"
- Do you want a graph or a graph?
- Have fun installing it.
- Still not great for introspection.
Very useful for deadlocks, blocking code, threaded app.
Simple to integrate:import socketconsole socketconsole.launch()
- CPython only.
- Doesn't work with gevent or eventlet monkeypatching.
- Doesn't work with greenthreads.
- Limited functionality.
- All the fun of Python threads.
- Pure Python!
- Changing code at runtime is for winners.
- Inspect all the things!
- With great power comes great responsibility.
- Requires threads or event loop.
- Still can't reach all state.
- Well, you wanted introspection.
- Has some Python helpers: pygdb, gdb-heap
- Seriously? Definitily only a a last resort.
- Universally supported.
- Powerful, extensible, 2-way.
- Helpful tools.
- Where "universal" means "runs on the JVM".
- Not as easy to monitor as you'd think.
Python needs this.
- Simple API to expose state.
- Separate publishing from reading, aggregating, etc.
- Language, platform, framework agnostic.
- Minimal & predictable performance impact.
- Optional persistence (e.g. post-mortems)
- 1-way (for now?)
mmap alows sharing memory between processes.
Language independent data structure:
- Series of fields (structs)
- Fields have label, type, and values.
Exposed in Python app as a model class.
Single writer, multi-reader
- No locks.
- No syscalls (write, read, send, recv, etc).
- All in userspace for readers & writers.
- Reading has no impact on writers.
- Fixed field sizes.
- Q: How are reads consistent without locks?
- A: Double buffering.