Profiling/Timeseries: Difference between revisions
From charlesreid1
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
* cpu, memory, threads, file size | * cpu, memory, threads, file size | ||
* where in structure, depth, iterations, etc. | * where in structure, depth, iterations, etc. | ||
Architecture: | |||
* Use [[Zmq]] | |||
* Zmq client is code running on device, populating message queue | |||
* Zmq server is server listening for messages, filtering takes place on server | |||
N queens problem: | N queens problem: | ||
| Line 10: | Line 16: | ||
* code instrumentation: current portion of tree (vector of queen placements), number of solutions found | * code instrumentation: current portion of tree (vector of queen placements), number of solutions found | ||
* profiling: netdata on host machine | * profiling: netdata on host machine | ||
[[Category:Python]] | |||
[[Category:2018]] | |||
[[Category:February 2018]] | |||
Latest revision as of 21:42, 17 February 2018
Here's what we're doing:
- Running CPU intensive code
- cpu, memory, threads, file size
- where in structure, depth, iterations, etc.
Architecture:
- Use Zmq
- Zmq client is code running on device, populating message queue
- Zmq server is server listening for messages, filtering takes place on server
N queens problem:
- searching for number of ways to arrange n queens on the chessboard
- code instrumentation: current portion of tree (vector of queen placements), number of solutions found
- profiling: netdata on host machine