Stage 5, day 1:
I did try to improve my client performance by implementing the idea that I wrote about in the last post. Performances appear to be slightly improved but not enough to escape the fatal fate of freezing due to processing saturation.
It seems like something is taking more time to perform as time goes... but oh well, I think that I'm going to throw the towel on this one. I'm not sure it would give me anything to solve that particular issue. I'll simply upgrade my desktop with a bigger machine and be done with that annoying issue.
If there was a good profiler existing, I could maybe give that a try to get some insight about what is dragging down the client... Right now, I'm just shooting in the dark.... but I'm not absolutely sure anymore that the problem comes from the tables rendering...
Update:
A new idea did pop. I have 11 time series/arrays per pair. There is currently 155 pairs. So that makes 1705 arrays. Each array can reach the maximum size of # of seconds in a day (86400).
I'm going to check if those arrays memory is pre-allocated. If not, everytime that I append an element (this happens every second), the reallocation would trigger a lot of memory copies (up to 1705*86400 copies!). Yes pretty sure that I have my performance dragging bastard...
Update #2:
My last intuition was good. CPU usage of the client is now stable! I cannot think of a better way to start a new BASE stage!
I did try to improve my client performance by implementing the idea that I wrote about in the last post. Performances appear to be slightly improved but not enough to escape the fatal fate of freezing due to processing saturation.
It seems like something is taking more time to perform as time goes... but oh well, I think that I'm going to throw the towel on this one. I'm not sure it would give me anything to solve that particular issue. I'll simply upgrade my desktop with a bigger machine and be done with that annoying issue.
If there was a good profiler existing, I could maybe give that a try to get some insight about what is dragging down the client... Right now, I'm just shooting in the dark.... but I'm not absolutely sure anymore that the problem comes from the tables rendering...
Update:
A new idea did pop. I have 11 time series/arrays per pair. There is currently 155 pairs. So that makes 1705 arrays. Each array can reach the maximum size of # of seconds in a day (86400).
I'm going to check if those arrays memory is pre-allocated. If not, everytime that I append an element (this happens every second), the reallocation would trigger a lot of memory copies (up to 1705*86400 copies!). Yes pretty sure that I have my performance dragging bastard...
Update #2:
My last intuition was good. CPU usage of the client is now stable! I cannot think of a better way to start a new BASE stage!
