Open tomara-x opened 3 weeks ago
when an op string is changed in command_parser we call str_to_net.. here we can do the same but this time we set another component an op number/enum (benchmark) this means we do the string comparing once an op is changed and then process only does a quick number comparison
lol
https://github.com/tomara-x/quartz/issues/30#issuecomment-1903398124
you forgot that the number of options is a multiplier here. so it's O(number of entities in queue * number of possible ops)
7c9e4a4 cuts it down to 1.47ms.. i was hoping for a little more cause i was hoping the string comparison was the heaviest thing, but still good
it's not bad, but currently process is approaching the no-no-land with an MTPC of 2.12 ms (this isn't bad)
being one big lump of code makes it hard to tell what's going on there. it would be much easier if things were split into smaller systems.. somehow