![]() But what the user does not always understand is that when you press space bar to open a deal, lots and lots of things are happening in Murex: the trade number is sent from the client to the application server. This is usually this type of performance which is ignored as 1s to open a trade or.1s does not seem like a big change to the user. In the list above, I’m referring to opening details, stickyness. One could argue that they’re both the same but let me explain:The UX ones are the ones which 1s or 2, for which timing is hard or imprecise. ![]() Since the new GUI, login, password, group are almost instant, but the actual session start when you enter a menu usually feels slow– Opening details: bonds, trades, counterparts, etc– The feeling that the system is sometimes a bit sticky, where actions take 1s or so when you expect them to be instant– Simulation loading– Accounting generation– Saving tradesThere are, in my opinion, 2 types of Murex performance issues: the user experience type and the structural ones. ![]() On the contrary, I’d like to take precise examples of what users frequently report:– Actual session start.
0 Comments
Leave a Reply. |