You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point, it's kinda obvious that Onix has stalled out. I regret nothing, in that I learned a metric ton about SQLAlchemy, CICD, packaging, documentation...
but at the end of the day, Onix is probably over-engineered.
I'd like to spec out an "80/20" stats rewrite solution--something that's robust and easily maintained, but not nearly as complex as Onix.
I'm thinking:
preserve the current workstream (read logs into intermediate files, process intermediate files into stats)
clean up and modularize code, adhering to coding best practices (four spaces instead of tabs!)
some amount of unit tests (probably more for the high level stuff like the tier update code, rather than the low-level log-reading)
move as much of the bash logic into python as possible (glob! concurrent.futures!)
optimize workstream by doing stuff like computing stats for all baselines at once
pull code from Onix where appropriate (Contexts are nice)
py3 only -- I just find it super painful to write py2 code now. Don't worry about pypy--if I want performance, I'll see if I can numbafy anything.
I'm thinking the rewrite will live in this repo.
It's probably still going to be months before I can get around to tackling this, but the reduction in scope should make this actually attainable.
The text was updated successfully, but these errors were encountered:
At this point, it's kinda obvious that Onix has stalled out. I regret nothing, in that I learned a metric ton about SQLAlchemy, CICD, packaging, documentation...
but at the end of the day, Onix is probably over-engineered.
I'd like to spec out an "80/20" stats rewrite solution--something that's robust and easily maintained, but not nearly as complex as Onix.
I'm thinking:
I'm thinking the rewrite will live in this repo.
It's probably still going to be months before I can get around to tackling this, but the reduction in scope should make this actually attainable.
The text was updated successfully, but these errors were encountered: