Cycle 22 (v2 cycle #4), day 3:
Many things did happen all at the same time.
I am really close to break the second transaction fee level by reaching the $100K last 30 days trading volume. I am currently at $87K.
It is crazy how some glitches that are in plain sight just go unnoticed because of the assumptions that you make. You just add some log to track something totally unrelated and it makes reevaluate your assumptions and then suddenly you get to see the obvious and what is wrong with the code is doing.
It did happen just right now.
I like the process. This is how you learn all the nuance of a certain field and become an expert.
As I was looking for ways to measure my latency with the exchange. I started calculate it locally. The problem is that it makes me query the system time through a costly system call. This is a bad design since I process millions of updates every few minutes. That means that I am doing millions of system calls every minute.
Then, I tried to figure out if I could not instead use the timestamps contained in the updates. By evaluating this idea, It made "see" that the condition to reevaluate the trading opportunities affected by this update was flawed.
Next trade server upgrade with those changes might affect the trading frequency of my system.
Many things did happen all at the same time.
I am really close to break the second transaction fee level by reaching the $100K last 30 days trading volume. I am currently at $87K.
It is crazy how some glitches that are in plain sight just go unnoticed because of the assumptions that you make. You just add some log to track something totally unrelated and it makes reevaluate your assumptions and then suddenly you get to see the obvious and what is wrong with the code is doing.
It did happen just right now.
I like the process. This is how you learn all the nuance of a certain field and become an expert.
As I was looking for ways to measure my latency with the exchange. I started calculate it locally. The problem is that it makes me query the system time through a costly system call. This is a bad design since I process millions of updates every few minutes. That means that I am doing millions of system calls every minute.
Then, I tried to figure out if I could not instead use the timestamps contained in the updates. By evaluating this idea, It made "see" that the condition to reevaluate the trading opportunities affected by this update was flawed.
Next trade server upgrade with those changes might affect the trading frequency of my system.
