diff options
author | gennyble <gen@nyble.dev> | 2025-02-25 20:17:30 -0600 |
---|---|---|
committer | gennyble <gen@nyble.dev> | 2025-02-25 20:17:30 -0600 |
commit | fef0a6c0eabf4c2471a0f080798dda3bf6017863 (patch) | |
tree | 53a0a0cf7117274d340dc5f4543eb1dc269627a4 | |
parent | 337b1faeeb414c5dad9a1b2cf80460a5e74eacbe (diff) | |
download | awake-fef0a6c0eabf4c2471a0f080798dda3bf6017863.tar.gz awake-fef0a6c0eabf4c2471a0f080798dda3bf6017863.zip |
update todo
-rw-r--r-- | TODO | 52 |
1 files changed, 34 insertions, 18 deletions
diff --git a/TODO b/TODO index caba2e8..a38033a 100644 --- a/TODO +++ b/TODO @@ -16,14 +16,21 @@ function where not all of the variables are available? I /really/ need to clean this up -(4) Make the statistics graphs have a concept of time - they do currently not a concept of time. all they do is pull - the latest 256 points and graph them regardless of whether or - not the full minute has elapsed or if more than a minute - elapsed. this is not very good. - get the last 256 points and correctly form them into a graph, - not taking more than one point per minute and skipping gaps - in data. +(6) Draw lower-on-average graph line last + Drawing the lower graph line last, for networking i am thinking + about specifically, will allow it to be drawn over the larger + one so it will let us see most of both fo them. This is working + now with TX/RX because we do more TX than RX, but that could + change and I would rather have it switch with smartness. + +(7) Stick 404's in the database + Mostly because I think it would be funny to see all the weird + endpoints the crawlers hit, and a bit to know what links I've + killed over the course of time. + +[next todo number: 8] + +# DONE (5) Only grab a data sample every minute related to (4). currently we grab a datapoint on boot always, @@ -34,14 +41,23 @@ on boot, before the first point, check when the last sample was taken and wait long enough to be a minute apart if needed. -(6) Draw lower-on-average graph line last - Drawing the lower graph line last, for networking i am thinking - about specifically, will allow it to be drawn over the larger - one so it will let us see most of both fo them. This is working - now with TX/RX because we do more TX than RX, but that could - change and I would rather have it switch with smartness. + done :) + we grab the last meminfo sample and wait until a minute after + that one to start data collection again. -(7) Stick 404's in the database - Mostly because I think it would be funny to see all the weird - endpoints the crawlers hit, and a bit to know what links I've - killed over the course of time. \ No newline at end of file +(4) Make the statistics graphs have a concept of time + they do currently not a concept of time. all they do is pull + the latest 256 points and graph them regardless of whether or + not the full minute has elapsed or if more than a minute + elapsed. this is not very good. + get the last 256 points and correctly form them into a graph, + not taking more than one point per minute and skipping gaps + in data. + + done :) + we now go through the samples and place them correctly in + time-slots. this both removes too-many-per-minute as well + as lets us display gaps in time. + The type /did/ have to change from [usize; 256] to an + [Option<usize>; 256], though. but i'd rather represent + gaps as nothing instead of as 0, which is for-sure something. \ No newline at end of file |