cycle 2. Stage 3, day 16:
almost a week has passed since last entry.
last week has been very busy for crypto trading. My system trading pattern did change a lot compared to what it used to be in the last month.
Due to the volatility spike, my system made more normal size arbitrage trades than my new micro trading strategy.
My system did stumble on a bunch of small bugs that I have kept me busy pretty much the whole week putting on hold my regular planning tasks.
The crypto crash is a bit worrying to me... The amount of income that my system is generating has remained constant when nominated in crypto but once converted in fiat, it got practically slashed in half.
I guess that if I leverage this situation to maintain my income in fiat stable, it will have the effect of doubling it when crypto value returns to its previous value down the road.
I was fixing what I though to be the very last remaining glitch from the current server version when I spotted code in a very low-level module that is called millions of time in the hot path. I have found a way to simplify it by removing a conditional branch and by removing an unnecessary variable assignment.
It seems like nothing. 2 lines max got removed but this code is called so much and branching is so expensive on x86-64 platform that this very simple change made a very significant difference in the system execution time. This is cool. This code is over 10 years old. I did not expect to find improvement opportunities there. That has been a very nice surprise today.
Bottomline, I am drifting a bit since last week but good stuff is happening nonetheless...
almost a week has passed since last entry.
last week has been very busy for crypto trading. My system trading pattern did change a lot compared to what it used to be in the last month.
Due to the volatility spike, my system made more normal size arbitrage trades than my new micro trading strategy.
My system did stumble on a bunch of small bugs that I have kept me busy pretty much the whole week putting on hold my regular planning tasks.
The crypto crash is a bit worrying to me... The amount of income that my system is generating has remained constant when nominated in crypto but once converted in fiat, it got practically slashed in half.
I guess that if I leverage this situation to maintain my income in fiat stable, it will have the effect of doubling it when crypto value returns to its previous value down the road.
I was fixing what I though to be the very last remaining glitch from the current server version when I spotted code in a very low-level module that is called millions of time in the hot path. I have found a way to simplify it by removing a conditional branch and by removing an unnecessary variable assignment.
It seems like nothing. 2 lines max got removed but this code is called so much and branching is so expensive on x86-64 platform that this very simple change made a very significant difference in the system execution time. This is cool. This code is over 10 years old. I did not expect to find improvement opportunities there. That has been a very nice surprise today.
Bottomline, I am drifting a bit since last week but good stuff is happening nonetheless...
