Performance challenges for OMERO.server
Aug. 14th, 2017 10:32 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
mtbcBack in May I had mentioned,
The server permissions work that I am doing was meant to have been released long ago. Enforcing a later hard security requirement caused some performance issues that took me some weeks to investigate and fix or at least work around. The release date was pushed to what is now fairly soon and more performance issues have raised their head, thanks in part to tougher testing that I recently suggested. I noted some ideas that may help but, as has been typical, luck has not smiled upon me which may be par for the course when wrestling complex legacy code, based on an equally complex enterprise software stack, so that it can manage current-scale data such as the Image Data Resource. I still have more ideas to try, perhaps even more to have, but I cannot promise to fix the issues on time nor am I sure that it would take less than a fundamental redesign.
On the one hand, my coworkers understand that I am wrestling with difficult issues and will help where they can. Just today one of them took one another task off my plate and has probably finished it off. On the other hand, being ongoingly at the center of delayed code with significant technical risk does not leave me feeling comfortably relaxed.
More recently in working on extending our server's permissions system and especially in then fixing the performance issues I thus caused, I have not been at all sure how many weeks the work would take nor how possible I would find it at all, which of course is a stressful uncertainty.I now seem to be back in that joyless realm.
The server permissions work that I am doing was meant to have been released long ago. Enforcing a later hard security requirement caused some performance issues that took me some weeks to investigate and fix or at least work around. The release date was pushed to what is now fairly soon and more performance issues have raised their head, thanks in part to tougher testing that I recently suggested. I noted some ideas that may help but, as has been typical, luck has not smiled upon me which may be par for the course when wrestling complex legacy code, based on an equally complex enterprise software stack, so that it can manage current-scale data such as the Image Data Resource. I still have more ideas to try, perhaps even more to have, but I cannot promise to fix the issues on time nor am I sure that it would take less than a fundamental redesign.
On the one hand, my coworkers understand that I am wrestling with difficult issues and will help where they can. Just today one of them took one another task off my plate and has probably finished it off. On the other hand, being ongoingly at the center of delayed code with significant technical risk does not leave me feeling comfortably relaxed.
